| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: confusing archive_command example |
| Date: | 2010-03-31 23:45:16 |
| Message-ID: | 201003312345.o2VNjGW24641@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > As far as "...", those are used to show only the important changes in
> > the string, which I think is the right approach, but I did change the
> > line so the dots are not right up against slashes:
> > archive_command = 'test ! -f ... %f && cp %p ... %f'
>
> This is *not* an improvement, because it makes it look like the %f is a
> separate command argument. Please revert if you can't think of
> something better.
What about:
archive_command = 'test ! -f ...%f && cp %p ...%f'
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-31 23:46:49 | Re: confusing archive_command example |
| Previous Message | Tom Lane | 2010-03-31 23:44:15 | Re: confusing archive_command example |