From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jaume Sabater <jsabater(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Warm standby recovery failure |
Date: | 2009-02-04 02:27:23 |
Message-ID: | dcc563d10902031827y36fe4c41x3cf82d39713ad55e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Jan 30, 2009 at 7:52 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jaume Sabater <jsabater(at)gmail(dot)com> writes:
>> On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | raf | 2009-02-04 14:37:41 | Re: How to prevent users from creating tables |
Previous Message | Scott Marlowe | 2009-02-04 02:25:37 | Re: Totally inappropriate by-line for a major representative of this organization |