| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | 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:12:01 |
| Message-ID: | 53F233E1.3030605@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
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.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-08-18 17:12:49 | Re: [DOCS] JDBC documentation - issue report |
| Previous Message | Christopher Barham | 2014-08-18 13:18:35 | JDBC documentation - issue report |