Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 10331B5DC02
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri,  7 Oct 2011 06:26:53 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 51247-04; Fri,  7 Oct 2011 09:26:47 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from uvena.de (uvena.de [79.140.41.123])
	by mail.postgresql.org (Postfix) with ESMTP id D9368B5DC0C;
	Fri,  7 Oct 2011 06:26:46 -0300 (ADT)
Received: from [141.35.39.175] (c319808.zuv.uni-jena.de [141.35.39.175])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by uvena.de (Postfix) with ESMTPSA id C062C254057;
	Fri,  7 Oct 2011 09:27:43 +0000 (UTC)
Message-ID: <4E8EC5D6.7080308@frank.uvena.de>
Date: Fri, 07 Oct 2011 11:26:46 +0200
From: Frank Lanitz <frank@frank.uvena.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: pgsql-admin@postgresql.org, pgsql-general@postgresql.org
Subject: Standby server witching into master role after import failure
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.404 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504
X-Spam-Level: 
X-Archive-Number: 201110/24
X-Sequence-Number: 38476

Hi folks,

I've got an issue I'm currently investigating and I'm not 100 sure about
the root cause.
The setup is pretty easy: A standby server via PITR is importing
WAL-files from master server. During this import it appears there has
been an error which cause the standby to finish the importing and going
live. I'm copying in LOG-file pars I tried to translate to English
(server running de_DE)

< 2011-09-28 19:38:26 CEST  >LOG:  unexpected page address 8B/5A000000
at logfile 144, Segment 1, Offset 0
< 2011-09-28 19:38:26 CEST  >LOG:  Redo done by 90/1EB48
< 2011-09-28 19:38:26 CEST  >LOG:  last completed transaction was
at logtime 2011-09-28 19:37:04.605199+02
< 2011-09-28 19:38:26 CEST  >LOG:  Logdatei 000000010000009000000000
recovered from achive
< 2011-09-28 19:39:26 CEST  >LOG:  choosen new Timeline-ID: 2
< 2011-09-28 19:40:26 CEST  >LOG:  Recover from archive finished

Obviously there have been an issue on WAL-file. But any chance to get
any detail what went wrong and what can be done to prevent such things
in future?

It's all 8.4 running on SLES11 SP1 AMD64

Cheers,
Frank