| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, 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:31:12 |
| Message-ID: | 5718.1408383072@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> 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.
If you want to remove the last line of this:
#archive_command = '' # command to use to archive a logfile segment
# placeholders: %p = path of file to archive
# %f = file name only
# e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'
I'm okay with that. But if you want to remove the sample command from the
SGML docs I'm going to push back a bit harder...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-08-19 17:19:34 | Re: Sample archive_command is still problematic |
| Previous Message | Magnus Hagander | 2014-08-18 17:13:34 | Re: Sample archive_command is still problematic |