Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 21CC29FB2FE for ; Sun, 25 Mar 2007 21:57:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 54745-03 for ; Sun, 25 Mar 2007 21:57:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 135D39FB269 for ; Sun, 25 Mar 2007 21:57:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l2Q0vl19001626; Sun, 25 Mar 2007 20:57:48 -0400 (EDT) To: Warren Little cc: pgsql-admin@postgresql.org Subject: Re: trying to run PITR recovery In-reply-to: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com> References: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com> Comments: In-reply-to Warren Little message dated "Fri, 23 Mar 2007 17:16:08 -0600" Date: Sun, 25 Mar 2007 20:57:47 -0400 Message-ID: <1625.1174870667@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/185 X-Sequence-Number: 25009 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 ... regards, tom lane