Re: archive_command vs. cp -i - Mailing list pgsql-admin

From Tom Lane
Subject Re: archive_command vs. cp -i
Date
Msg-id 20654.1308333896@sss.pgh.pa.us
Whole thread Raw
In response to Re: archive_command vs. cp -i  (John Rouillard <rouilj@renesys.com>)
Responses Re: archive_command vs. cp -i  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
John Rouillard <rouilj@renesys.com> writes:
>> On Fri, Jun 17, 2011 at 12:32 PM, Kevin Grittner
>> Kevin.Grittner@wicourts.gov> wrote:
>>>> This could be reproduced on CentOS 5.6, RHEL4, and Ubuntu 10.04.
>>> I've confirmed on SLES 10 and Ubuntu 9, too.

> Not really surprising since choosing to not copy a file isn't really
> an indication of an error when copying a file so...

> I get the same result (0 exit status) on solaris 8 and solaris 10 with
> /bin/cp.  I wonder what platform the example worked on.

cp does behave as the example suggests for me, on OS X and HPUX.  I
suspect Bruce tested it on some BSD variant before putting it in the
docs.  That would suggest that it probably works that way on most (all?)
BSDen.  Still, if the GNU version doesn't act that way, we have a
problem.

The test-and-cp approach seems the most likely to be portable.

            regards, tom lane

pgsql-admin by date:

Previous
From: John Rouillard
Date:
Subject: Re: archive_command vs. cp -i
Next
From: Tom Lane
Date:
Subject: Re: archive_command vs. cp -i