Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id CC26E1337B90
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  2 Feb 2011 19:57:44 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 93740-01 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  2 Feb 2011 23:57:37 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 583E61337B8D
	for <pgsql-admin@postgresql.org>; Wed,  2 Feb 2011 19:57:37 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p12Nva5q005485;
	Wed, 2 Feb 2011 18:57:36 -0500 (EST)
To: Ray Stell <stellr@cns.vt.edu>
cc: pgsql-admin@postgresql.org
Subject: Re: unexpected pageaddr 
In-reply-to: <20110202234321.GA22981@cns.vt.edu> 
References: <20110202204651.GA10182@cns.vt.edu>
 <5031.1296689542@sss.pgh.pa.us>
	<20110202234321.GA22981@cns.vt.edu>
Comments: In-reply-to Ray Stell <stellr@cns.vt.edu>
	message dated "Wed, 02 Feb 2011 18:43:21 -0500"
Date: Wed, 02 Feb 2011 18:57:36 -0500
Message-ID: <5484.1296691056@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201102/6
X-Sequence-Number: 36645

Ray Stell <stellr@cns.vt.edu> writes:
> On Wed, Feb 02, 2011 at 06:32:22PM -0500, Tom Lane wrote:
>> "unexpected pageaddr" is just one of the standard tests for detecting
>> end of WAL, so I don't think this is anything to be surprised about.
>> It looks to me like the standby applied all the WAL it had and then
>> connected to the master for more.

> thanks, Tom.  I suppose it's the order that trips me up:

>  starts at 65...
>  reached a 66...
>  unexpected at 62...

Well, the point of the "unexpected pageaddr" message is exactly that the
WAL location it found in the next file wasn't the expected next location
in sequence (which would have to be something larger than 0/66000000).
This indicates that the next file isn't really new WAL, but a segment
file that was recycled (by renaming it to a higher file number) but not
yet overwritten with new data.

			regards, tom lane