Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XIjF9-0008RD-Tu for pgsql-docs@arkaria.postgresql.org; Sat, 16 Aug 2014 19:02:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XIjF8-0002mB-F6 for pgsql-docs@arkaria.postgresql.org; Sat, 16 Aug 2014 19:02:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XIjF7-0002lw-IF for pgsql-docs@postgresql.org; Sat, 16 Aug 2014 19:02:21 +0000 Received: from mail-we0-f172.google.com ([74.125.82.172]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XIjEx-0005O5-PJ for pgsql-docs@postgresql.org; Sat, 16 Aug 2014 19:02:19 +0000 Received: by mail-we0-f172.google.com with SMTP id x48so3510506wes.31 for ; Sat, 16 Aug 2014 12:02:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=G4IFJiq7OqvGSsSWpcdlj8kwCbn0iTKR2XLOgW4yB4E=; b=FdOqRUoudP+m2EhMWhYuFTptis6jRY2hd6A3Wv8R/x6n3ARf7pHdwDVLF4etm+y60P vZoZ9NNZbsKvaYF6/88WwOnZHzIBI5rMr5ovPQIgENBawoIsoON9pbT15EIU9FyEmNxY gPft1K0HrlSecYdvNfpy05LcVXfOhcBKzx3Bjn4i/7xr6bzz8l7mNrwPy/aS0GizPaiv nTRgSuWhgnNjfZ1NrmX1d4hepBK9ENFBu27OzLrGELFr/4NhGhlYHizVooS8ZINyQxjF WWtzrCXTwO4xh02J2KT+9hhWSuzhQ9JZT9HOzXCl/ADiv96Nar/xYfexRt52UIvMd5lY e56w== X-Gm-Message-State: ALoCoQlMmdgqQC9I211/ujvPT4o6WTHLadB7+qkZm21tOQuD+9VN8t4YBzbwF27Q86Xg1RSmvb0N MIME-Version: 1.0 X-Received: by 10.194.237.194 with SMTP id ve2mr30121593wjc.89.1408215729378; Sat, 16 Aug 2014 12:02:09 -0700 (PDT) Received: by 10.195.13.45 with HTTP; Sat, 16 Aug 2014 12:02:09 -0700 (PDT) In-Reply-To: <1407965034.12878.YahooMailNeo@web122304.mail.ne1.yahoo.com> References: <53E5603B.5040102@agliodbs.com> <1407777686.41146.YahooMailNeo@web122306.mail.ne1.yahoo.com> <0F73426A2EA544878BCAC33BB989D671@maumau> <53EBCCEA.3090604@gmx.net> <1407965034.12878.YahooMailNeo@web122304.mail.ne1.yahoo.com> Date: Sat, 16 Aug 2014 21:02:09 +0200 Message-ID: Subject: Re: Sample archive_command is still problematic From: Magnus Hagander To: Kevin Grittner Cc: Peter Eisentraut , MauMau , Josh Berkus , "pgsql-docs@postgresql.org" Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Wed, Aug 13, 2014 at 11:23 PM, Kevin Grittner wrote: > The above is regarding WAL file archiving -- I'm not putting down > streaming replication. Of course, what I would have *really* liked > is a WAL receiver that could write out normal-looking WAL files for > archiving purposes and pass through the WAL stream to a hot > standby. Last I checked (which was admittedly at least a couple > years back) there was no such utility, although I seem to remember > that Magnus had done some work that looked like it could be bent to > that end. I did. But I think that has mostly been superceded by replication slots now. As in, if you use pg_receivexlog with a specific replication slot, I believe you no longer need archive command at all, do you? Since the replication slot will block rotation of the WAL files until they are actually archived by pg_receivexlog (What my command did was have an archive command that looked back into pg_stat_replication to see if pg_receivexlog had received the data or not). It did not pass through any WAL stream though - you'd have your standby connect directly to the same master that pg_receivexlog connects to. What would be the actual reason for having that one do the passthrough itself? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs