| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, MauMau <maumau307(at)gmail(dot)com>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Sample archive_command is still problematic |
| Date: | 2014-08-18 17:13:34 |
| Message-ID: | CABUevEwgooP6gg5XbKAMZjrdML9dhLPp4Pavox3oGrE1UnW7zA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Aug 18, 2014 at 7:12 PM, Josh Berkus <josh(at)agliodbs(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-08-18 17:31:12 | Re: Sample archive_command is still problematic |
| Previous Message | Josh Berkus | 2014-08-18 17:12:49 | Re: [DOCS] JDBC documentation - issue report |