From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: "Martin Münstermann" <mmuenst@gmx.de>
To: pgsql-admin@postgresql.org
Subject: Re: archive_command vs. cp -i
Date: Fri, 17 Jun 2011 11:32:56 -0500
Message-ID: <4DFB3B68020000250003E7EA@gw.wicourts.gov> (raw)
In-Reply-To: <20110617084057.238070@gmx.net>
References: <20110617084057.238070@gmx.net>
"Martin Münstermann"<mmuenst@gmx.de> wrote:
> while setting up a new linux postgresql server, I checked my
> archive_command. I noticed that the usual "cp -i f1 f2 <
> /dev/null" did NOT as expected: It did not overwrite the file
> (PASS), but it returned zero (FAIL, should return error).
>
> This could be reproduced on CentOS 5.6, RHEL4, and Ubuntu 10.04.
I've confirmed on SLES 10 and Ubuntu 9, too.
> Should the BACKUP-ARCHIVING-WAL doc be changed?
I think so. Given the wide variety of platforms on which the
example could silently cause data loss, I *really* don't think we
want that in our docs. Someone could blithely copy it into
production without testing and not know they had it wrong until a
backup failed to restore.
-Kevin
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, mmuenst@gmx.de
Subject: Re: archive_command vs. cp -i
In-Reply-To: <4DFB3B68020000250003E7EA@gw.wicourts.gov>
References: <20110617084057.238070@gmx.net> <4DFB3B68020000250003E7EA@gw.wicourts.gov>
* 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