Received: from localhost (maia-4.hub.org [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 3CDFC9FB53D
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 25 Jun 2007 13:27:06 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 59133-06 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 25 Jun 2007 13:27:02 -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 ABCB29FB533
	for <pgsql-performance@postgresql.org>;
	Mon, 25 Jun 2007 13:27:01 -0300 (ADT)
thread-index: Ace3RbGpZWG3Z18gTsyytrGYwdDyKA==
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 12:27:15 -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" <simon@2ndquadrant.com>
To: "Dan Gorman" <dgorman@hi5.com>
Cc: <pgsql-performance@postgresql.org>
In-Reply-To: <D9E96F55-3AF6-4DC7-A68A-251567976E88@hi5.com>
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>
	<D9E96F55-3AF6-4DC7-A68A-251567976E88@hi5.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Mon, 25 Jun 2007 17:23:18 +0100
Message-ID: <1182788599.9276.598.camel@silverbirch.site>
MIME-Version: 1.0
X-Mailer: Evolution 2.6.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2007 16:27:16.0281 (UTC)
	FILETIME=[B18D6A90:01C7B745]
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200706/576
X-Sequence-Number: 25609

On Mon, 2007-06-25 at 08:28 -0700, Dan Gorman wrote:
> I took several snapshots. In all cases the FS was fine. In one case  
> the db looked like on recovery it thought there were outstanding  
> pages to be written to disk as seen below and the db wouldn't start.
> 
> Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [9-1] 2007-06-21  
> 00:39:43 PDTLOG:  redo done at 71/99870670
> 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

OK, please put log_min_messages = DEBUG2 and re-run the recovery please.

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