Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 7D2459FBAC8 for ; Mon, 25 Jun 2007 13:59:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 71231-01-2 for ; Mon, 25 Jun 2007 13:59:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 938BA9FB4E1 for ; Mon, 25 Jun 2007 13:59:47 -0300 (ADT) thread-index: Ace3SkVE/54bNitRQFKQS/fn6++kzg== Received: from [172.24.32.12] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 25 Jun 2007 13:00:00 -0400 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4073 Subject: Re: PITR Backups From: "Simon Riggs" To: "Tom Lane" Cc: "Dan Gorman" , "Koichi Suzuki" , "Toru SHIMOGAKI" , In-Reply-To: <367.1182789258@sss.pgh.pa.us> References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com> <9761.1182472005@sss.pgh.pa.us> <467B3459.9030808@oss.ntt.co.jp> <1182509748.9276.178.camel@silverbirch.site> <467F938F.1030708@oss.ntt.co.jp> <1182777963.9276.582.camel@silverbirch.site> <367.1182789258@sss.pgh.pa.us> Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 25 Jun 2007 17:56:06 +0100 Message-ID: <1182790567.9276.609.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Jun 2007 17:00:00.0531 (UTC) FILETIME=[44562E30:01C7B74A] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/578 X-Sequence-Number: 25611 On Mon, 2007-06-25 at 12:34 -0400, Tom Lane wrote: > Dan Gorman writes: > > Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [9-1] 2007-06-21 > > 00:39:43 PDTLOG: redo done at 71/99870670 This is mid-way through an xlog file. > > Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [10-1] 2007-06-21 > > 00:39:43 PDTWARNING: page 28905 of relation 1663/16384/76718 was > > uninitialized > > ... lots of these ... > > Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [40-1] 2007-06-21 > > 00:39:43 PDTPANIC: WAL contains references to invalid pages > > (BTW, you'll find putting a space at the end of log_line_prefix > does wonders for log readability.) > > Reformatting and sorting, we have > > WARNING: page 28900 of relation 1663/16384/76718 was uninitialized > WARNING: page 28902 of relation 1663/16384/76718 was uninitialized > WARNING: page 26706 of relation 1663/16384/76719 was uninitialized > WARNING: page 26708 of relation 1663/16384/76719 was uninitialized Those two are interesting because we appear to have two valid pages in the middle of some uninitialized ones. That implies were not looking at an unapplied truncation. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com