Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id D6CD59FB5CA for ; Fri, 30 Mar 2007 11:23:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 54754-03 for ; Fri, 30 Mar 2007 11:23:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from atherton-ex-02.meridias.local (exchange.meridiascapital.com [65.90.55.79]) by postgresql.org (Postfix) with ESMTP id 573C19FB5D1 for ; Fri, 30 Mar 2007 11:23:10 -0300 (ADT) Received: from [192.168.11.11] ([192.168.11.11]) by atherton-ex-02.meridias.local with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Mar 2007 08:23:07 -0600 In-Reply-To: <1175253394.4386.745.camel@silverbirch.site> References: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com> <1175253394.4386.745.camel@silverbirch.site> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: multipart/alternative; boundary=Apple-Mail-1--611108914 Message-Id: <5F414061-9F03-4580-9CD7-1458BA942530@MeridiasCapital.com> Cc: From: Warren Little Subject: Re: trying to run PITR recovery Date: Fri, 30 Mar 2007 08:23:06 -0600 To: Simon Riggs X-Mailer: Apple Mail (2.752.3) X-OriginalArrivalTime: 30 Mar 2007 14:23:07.0534 (UTC) FILETIME=[EFD092E0:01C772D6] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/231 X-Sequence-Number: 25055 --Apple-Mail-1--611108914 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed 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 --Apple-Mail-1--611108914 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 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:=A0 restored log = file
"000000010000011A000000FD" from = archive
@ 2007-03-23 05:57:35 MDTLOG:=A0 = incorrect resource manager data
checksum in = record at 11A/FD492B20
@ 2007-03-23 05:57:35 = MDTLOG:=A0 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"=A0
(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

The WAL file was clearly corrupt.=A0

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

These may also not work very = well at all, since many records depend upon

What would you suggest?

--=A0
=A0 Simon Riggs=A0 =A0 =A0 =A0 =A0 =A0 = =A0
=A0 EnterpriseDB =A0 http://www.enterprisedb.com
=



Warren = Little
Chief Technology Officer
Meridias Capital = Inc
ph 866.369.7763


=

= --Apple-Mail-1--611108914--