X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 28710D1B16E
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Thu, 22 Jul 2004 17:20:05 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 31957-08
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Thu, 22 Jul 2004 20:20:01 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by svr1.postgresql.org (Postfix) with ESMTP id 5110ED1B374
	for <pgsql-admin@postgresql.org>; Thu, 22 Jul 2004 17:19:55 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i6MKJrkB012174;
	Thu, 22 Jul 2004 16:19:53 -0400 (EDT)
To: Mark Kirkwood <markir@coretech.co.nz>
Cc: Simon Riggs <simon@2ndquadrant.com>, pgsql-admin@postgresql.org
Subject: Re: [HACKERS] Point in Time Recovery 
In-reply-to: <40FF1D88.30404@coretech.co.nz> 
References: <200407132242.i6DMgg612564@candle.pha.pa.us>
	<1089760416.17493.3327.camel@stromboli>
	<40F49AE9.2060805@familyhealth.com.au>
	<1089789682.17493.3890.camel@stromboli>
	<40FF1D88.30404@coretech.co.nz>
Comments: In-reply-to Mark Kirkwood <markir@coretech.co.nz>
	message dated "Thu, 22 Jul 2004 13:51:04 +1200"
Date: Thu, 22 Jul 2004 16:19:53 -0400
Message-ID: <12173.1090527593@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200407/254
X-Sequence-Number: 14322

Mark Kirkwood <markir@coretech.co.nz> writes:
> 2) Is is possible to make the recovery kick in even though pg_control 
> says the database state is shutdown?

Yeah, I think you are right: presence of recovery.conf should force a
WAL scan even if pg_control claims it's shut down.  Fix committed.

			regards, tom lane