Re: Warm standby recovery failure - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: Warm standby recovery failure
Date
Msg-id dcc563d10902031827y36fe4c41x3cf82d39713ad55e@mail.gmail.com
Whole thread Raw
In response to Re: Warm standby recovery failure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Fri, Jan 30, 2009 at 7: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'.

Plus, if you're using a system like rsync it uses checksums to make
sure the data transferred is correct if you use the -c (think that's
the one) switch.
--
When fascism comes to America, it will be the intolerant selling it as
diversity.

pgsql-admin by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Totally inappropriate by-line for a major representative of this organization
Next
From: raf
Date:
Subject: Re: How to prevent users from creating tables