From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command. |
Date: | 2011-06-18 13:19:54 |
Message-ID: | 15974.1308403194@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Thom Brown <thom(at)linux(dot)com> writes:
> On 18 June 2011 04:13, Bruce Momjian <bruce(at)momjian(dot)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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-06-18 13:28:48 | Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command. |
Previous Message | Dickson S. Guedes | 2011-06-18 13:11:58 | Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command. |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-06-18 13:21:39 | plpgsql performance - SearchCatCache issue |
Previous Message | Dickson S. Guedes | 2011-06-18 13:11:58 | Re: Re: [COMMITTERS] pgsql: Don't use "cp -i" in the example WAL archive_command. |