Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 7C8B99FB63F for ; Fri, 30 Mar 2007 12:38:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 10451-02 for ; Fri, 30 Mar 2007 12:38:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (webmail.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id F1DD19FB60D for ; Fri, 30 Mar 2007 12:38:36 -0300 (ADT) thread-index: Acdy4YNYfC8XRHryRKiCKtZ3qGNVNg== Received: from [192.168.0.22] ([85.211.147.35]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Mar 2007 11:38:49 -0400 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Subject: Re: trying to run PITR recovery From: "Simon Riggs" To: "Tom Lane" Cc: "Warren Little" , In-Reply-To: <1625.1174870667@sss.pgh.pa.us> References: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com> <1625.1174870667@sss.pgh.pa.us> Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 30 Mar 2007 16:34:51 +0100 Message-ID: <1175268891.4386.781.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Mar 2007 15:38:49.0625 (UTC) FILETIME=[831CA890:01C772E1] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/236 X-Sequence-Number: 25060 On Sun, 2007-03-25 at 20:57 -0400, Tom Lane wrote: > Warren Little writes: > > I'm testing my PITR recovery procedures and something doesn't look > > right. > > The following is from the logs upon starting postgres with > > recovery.conf file in place > > > @ 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 > > > 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. > > Perhaps you have a bad copy of that particular log segment file? > The "incorrect checksum" failure is normal in certain circumstances > (eg, where the system crashes partway through writing out a large > WAL record), which is why the code treats it as indicating the end > of WAL. But in this case it looks more like corrupt data ... Tom, I think there is a problem here. If we stop before the end of logs we should be incrementing the timeline id. I'm not going to think about it right now, but I'll think on that next week. Not the most likely problem we'll ever see, I grant you. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com