MIME-Version: 1.0
In-Reply-To: <53F233E1.3030605@agliodbs.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>
 <CABUevEwiaBWkgV+RX=Y77hauz-oKSo=7Tu7S7a8DN4dXGZSdTQ@mail.gmail.com>
 <WM!82507310e76be1df29048280e058916e28f087da5fbabb90b2b211e11d1cadd78895174bd7e489fa8d894cb824320620!@asav-2.01.com>
 <53F233E1.3030605@agliodbs.com>
Date: Mon, 18 Aug 2014 19:13:34 +0200
Message-ID: 
 <CABUevEwgooP6gg5XbKAMZjrdML9dhLPp4Pavox3oGrE1UnW7zA@mail.gmail.com>
Subject: Re: Sample archive_command is still problematic
From: Magnus Hagander <magnus@hagander.net>
To: Josh Berkus <josh@agliodbs.com>
Cc: Kevin Grittner <kgrittn@ymail.com>, Peter Eisentraut <peter_e@gmx.net>,
 MauMau <maumau307@gmail.com>,
 "pgsql-docs@postgresql.org" <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Mon, Aug 18, 2014 at 7:12 PM, Josh Berkus <josh@agliodbs.com> wrote:
> Magnus, Kevin:
>
> Two things:
>
> 1) pg_receivexlog doesn't help for users who need to archive from the
> master to cold storage (e.g. remote SAN, S3, whatever).  So we're going
> to still need an archive_command.

It can, but it's definitely ugly :) As in you can run pg_receivexlog
locally... (No, I am not seriously suggesting you should)


> 2) One reason users are using the "test -f" version of the archive
> command is that we put it in the same postgresql.conf.  I would suggest
> that we don't put *any* archive command in the sample postgresql.conf,
> since there is no command we can supply which isn't a potential foot-gun.

+1.

-- 
 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