From: Warren Little <Warren.Little@MeridiasCapital.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: trying to run PITR recovery
Date: Fri, 30 Mar 2007 08:23:06 -0600
Message-ID: <5F414061-9F03-4580-9CD7-1458BA942530@MeridiasCapital.com> (raw)
In-Reply-To: <1175253394.4386.745.camel@silverbirch.site>
References: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com>
<1175253394.4386.745.camel@silverbirch.site>
Simon,
I have no issues with how the error was handled, just the
notification that an error was encountered.
> @ 2007-03-23 05:57:33 MDTLOG: restored log file
> "000000010000011A000000FD" from archive
> @ 2007-03-23 05:57:35 MDTLOG: incorrect resource manager data
> checksum in record at 11A/FD492B20
> @ 2007-03-23 05:57:35 MDTLOG: redo done at 11A/FD492210
The first message says it restored the file, the second message looks
like an error, but for myself, who does this process very seldom, its
hard to tell what exactly transpired.
On slightly different topic, is there some way to determine the
timeline of the corrupted segment, ie what was the original time of
the last restored transaction.
On Mar 30, 2007, at 5:16 AM, Simon Riggs wrote:
> On Fri, 2007-03-23 at 17:16 -0600, Warren Little wrote:
>
>> My concern is that there were many more logfiles to be played
>> following "00000010000011A000000FD"
>> (ie 000000010000011E0000005C) yet it appears the recovery stop at
>> that
>> point and called it good.
>> I would assume all WAL logs would be restored.
>
> I'm interested in your feedback here. How would you like it to have
> acted?
>
> The WAL file was clearly corrupt.
>
> 1. Don't continue and don't come up. Have the recovery fail. In
> order to
> bring the server up, we would have to restart recovery with an
> additional command to say "I note that my recovery has failed and
> would
> like recovery to come up at the last possible point."
>
> 2. Attempt to continue after we fail the CRC check. This is both
> dangerous and in many cases won't work either, since this is one of
> the
> normal ending points.
>
> 3. Continue after a CRC check, don't attempt to apply the records,
> just
> look at them to determine if they look correct. i.e. see if the CRC
> error applies to just that record
>
> 4. Add a command to ignore specific WAL records
> ignore_record = '11A/FD492B20'
>
> These may also not work very well at all, since many records depend
> upon
> previous data changes, so could quickly end in further errors.
>
> What would you suggest?
>
> --
> Simon Riggs
> EnterpriseDB http://www.enterprisedb.com
>
>
Warren Little
Chief Technology Officer
Meridias Capital Inc
ph 866.369.7763
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: Warren.Little@MeridiasCapital.com, simon@2ndquadrant.com
Subject: Re: trying to run PITR recovery
In-Reply-To: <5F414061-9F03-4580-9CD7-1458BA942530@MeridiasCapital.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