From: Lee Azzarello <lee@dropio.com>
To: pgsql-admin@postgresql.org
Subject: Re: Warm standby recovery failure
Date: Tue, 3 Feb 2009 16:40:55 -0500
Message-ID: <16b031c0902031340j2467e238u9028485a8ef61043@mail.gmail.com> (raw)
In-Reply-To: <8207.1233327145@sss.pgh.pa.us>
References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com>
<14981.1233278521@sss.pgh.pa.us>
<3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com>
<8207.1233327145@sss.pgh.pa.us>
thank you all for your help. It was indeed my copy script that
destroyed the database. I now understand that postgresql shouldn't be
concerned with validating a WAL segment, that's the responsibility of
the script that hands the segment to postgres.
-lee
On Fri, Jan 30, 2009 at 9:52 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jaume Sabater <jsabater@gmail.com> writes:
>> 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?
>
> That seems like using a sledgehammer to swat a fly. The problem as
> I saw it was that the script was probably simply not checking for
> an error result from 'cp'.
>
> regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
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: lee@dropio.com
Subject: Re: Warm standby recovery failure
In-Reply-To: <16b031c0902031340j2467e238u9028485a8ef61043@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