From: Jaume Sabater <jsabater@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Warm standby recovery failure
Date: Fri, 30 Jan 2009 09:53:19 +0100
Message-ID: <3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com> (raw)
In-Reply-To: <14981.1233278521@sss.pgh.pa.us>
References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com>
<14981.1233278521@sss.pgh.pa.us>
On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> We probably should add a caution about this to the manual's discussion
> of how to write archiving scripts.
I presume you mean the copy/transfer process did not do its job
correctly, Tom. Therefore, I would advise using a script that compares
the MD5/SHA1 sums of the origin and destination files and retries the
copy/transfer process before returning an exit status to the server
(archive_command call). Do you think this would suffice?
--
Jaume Sabater
http://linuxsilo.net/
"Ubi sapientas ibi libertas"
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: jsabater@gmail.com
Subject: Re: Warm standby recovery failure
In-Reply-To: <3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com>
* 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