Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command. - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command.
Date
Msg-id BANLkTikh-a5ufD33QCBB06NR9zKPUZugcw@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command.
List pgsql-hackers
On Sat, Jun 18, 2011 at 10:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thom Brown <thom@linux.com> writes:
>> On 18 June 2011 04:13, Bruce Momjian <bruce@momjian.us> wrote:
>>> I tested on FreeBSD 7.4 and saw a 1 error return:
>
>> And on a Mac (so through Darwin 10.7.0 a BSD version too):
>
> Yeah, see yesterday's discussion on pgsql-admin.  I think the behavior
> with the error return may be a BSD-ism.  In any case, GNU cp does *not*
> do what we want, and that accounts for a sufficiently large fraction of
> machines in the field that I think it's just unsafe to suggest using
> "cp -i" so prominently.  There are too many people who'll just copy and
> paste the first example provided, especially if the warning to test it
> is buried several paragraphs later.

Anyway, you seem to have forgotten to fix the example of archive_command
in "24.3.5.1. Standalone Hot Backups".
    archive_command = 'test ! -f /var/lib/pgsql/backup_in_progress ||
cp -i %p /var/lib/pgsql/archive/%f < /dev/null'

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Patch - Debug builds without optimization
Next
From: Fujii Masao
Date:
Subject: Re: time-delayed standbys