From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ray Stell <stellr@cns.vt.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: unexpected pageaddr
Date: Wed, 02 Feb 2011 18:57:36 -0500
Message-ID: <5484.1296691056@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, stellr@cns.vt.edu
Subject: Re: unexpected pageaddr
In-Reply-To: <5484.1296691056@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox