Re: Sample archive_command is still problematic - Mailing list pgsql-docs

From Magnus Hagander
Subject Re: Sample archive_command is still problematic
Date
Msg-id CABUevEwgooP6gg5XbKAMZjrdML9dhLPp4Pavox3oGrE1UnW7zA@mail.gmail.com
Whole thread Raw
In response to Re: Sample archive_command is still problematic  (Josh Berkus <josh@agliodbs.com>)
List pgsql-docs
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/


pgsql-docs by date:

Previous
From: Josh Berkus
Date:
Subject: Re: JDBC documentation - issue report
Next
From: Tom Lane
Date:
Subject: Re: Sample archive_command is still problematic