From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Rouillard <rouilj@renesys.com>
Cc: Tim <elatllat@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: archive_command vs. cp -i
Date: Fri, 17 Jun 2011 14:04:56 -0400
Message-ID: <20654.1308333896@sss.pgh.pa.us> (raw)
In-Reply-To: <20110617172650.GG26732@renesys.com>
References: <20110617084057.238070@gmx.net>
<4DFB3B68020000250003E7EA@gw.wicourts.gov>
<BANLkTinjAm0nQ8Kosv7Q1u4=5UZj4jcFHQ@mail.gmail.com>
<20110617172650.GG26732@renesys.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, rouilj@renesys.com, elatllat@gmail.com
Subject: Re: archive_command vs. cp -i
In-Reply-To: <20654.1308333896@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox