Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id A3A44B5DBFC
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri, 26 Aug 2011 19:22:02 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 12558-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri, 26 Aug 2011 22:21:55 +0000 (UTC)
X-Greylist: delayed 00:09:40.120055 by SQLgrey-1.7.6
Received: from relay01.cambriumhosting.nl (relay01.cambriumhosting.nl
	[217.19.16.173])
	by mail.postgresql.org (Postfix) with ESMTP id AC2EDB5DBFA
	for <pgsql-admin@postgresql.org>; Fri, 26 Aug 2011 19:21:55 -0300 (ADT)
Received: from relay01.cambriumhosting.nl (localhost [127.0.0.1])
	by relay01.cambriumhosting.nl (Postfix) with ESMTP id 8202860002B4
	for <pgsql-admin@postgresql.org>; Sat, 27 Aug 2011 00:12:13 +0200 (CEST)
Received: from [192.168.13.15] (unknown [217.19.29.52])
	by relay01.cambriumhosting.nl (Postfix) with ESMTP id 63AEF600009C
	for <pgsql-admin@postgresql.org>; Sat, 27 Aug 2011 00:12:13 +0200 (CEST)
Message-ID: <4E581A3F.2020705@alpenjodel.de>
Date: Sat, 27 Aug 2011 00:12:15 +0200
From: gais <gais@alpenjodel.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
CC: pgsql-admin@postgresql.org
Subject: Re: Point-In-Time Recovery not working
References: <4E57C819.1010209@alpenjodel.de>
	<4E578883020000250004076B@gw.wicourts.gov>
In-Reply-To: <4E578883020000250004076B@gw.wicourts.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by ClamAV (clamav.cambrium.nl) at relay.cambriumhosting.nl
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.879 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, MISSING_HEADERS=1.021
X-Spam-Level: 
X-Archive-Number: 201108/214
X-Sequence-Number: 38201

I've tried to follow the directions as closely as possible, but still 
the server won't start. I do get a different PANIC:

2011-08-26 23:55:08 CEST LOG:  database system was shut down at 
2011-08-26 22:08:35 CEST
2011-08-26 23:55:08 CEST LOG:  starting archive recovery
2011-08-26 23:55:08 CEST LOG:  restore_command = 'cp 
/var/lib/postgresql/8.3/main/archive/%f %p'
cp: cannot stat `/var/lib/postgresql/8.3/main/archive/00000001.history': 
No such file or directory
2011-08-26 23:55:08 CEST LOG:  restored log file 
"0000000100000001000000EE" from archive
2011-08-26 23:55:08 CEST LOG:  unexpected pageaddr 1/EB01C000 in log 
file 1, segment 238, offset 114688
2011-08-26 23:55:08 CEST LOG:  invalid primary checkpoint record
2011-08-26 23:55:08 CEST LOG:  restored log file 
"0000000100000001000000EE" from archive
2011-08-26 23:55:08 CEST LOG:  invalid xl_info in secondary checkpoint 
record
2011-08-26 23:55:08 CEST PANIC:  could not locate a valid checkpoint record
2011-08-26 23:55:08 CEST LOG:  startup process (PID 8975) was terminated 
by signal 6: Aborted
2011-08-26 23:55:08 CEST LOG:  aborting startup due to startup process 
failure

Somehow I think the database files I used to restore are inconsistent 
with the WAL's. Is there a workaround or am I still doing something 
completely foolish?


> Not based very closely on the documentation.  Please read the
> "Recovering using a Continuous Archive Backup" subsection closely
> and follow the directions there.  In particular, initdb is not run
> as part of the recovery.  If you follow the directions step by step,
> you should get farther.  If you still have problems, feel free to
> post again.
>
> -Kevin