| From: | Lee Azzarello <lee(at)dropio(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Warm standby recovery failure |
| Date: | 2009-02-03 21:40:55 |
| Message-ID: | 16b031c0902031340j2467e238u9028485a8ef61043@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(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'.
>
> regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raf | 2009-02-04 00:52:22 | How to prevent users from creating tables |
| Previous Message | Carol Walter | 2009-02-03 17:23:26 | Re: Permissions to a schema |