From: Ray Stell <stellr@cns.vt.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: unexpected pageaddr
Date: Wed, 2 Feb 2011 18:43:21 -0500
Message-ID: <20110202234321.GA22981@cns.vt.edu> (raw)
In-Reply-To: <5031.1296689542@sss.pgh.pa.us>
References: <20110202204651.GA10182@cns.vt.edu>
<5031.1296689542@sss.pgh.pa.us>
On Wed, Feb 02, 2011 at 06:32:22PM -0500, Tom Lane wrote:
> Ray Stell <stellr@cns.vt.edu> writes:
> > Streaming replication standby moved from 9.0.2->9.0.3 logs this up
> > startup:
>
> > database system was shut down in recovery at 2011-02-02 15:28:51 EST
> > entering standby mode
> > redo starts at 0/65000170
> > consistent recovery state reached at 0/66000000
> > unexpected pageaddr 0/62000000 in log file 0, segment 102, offset 0
> > database system is ready to accept read only connections
> > streaming replication successfully connected to primary
>
> > Is the standby hurt?
>
> "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.
>
> regards, tom lane
thanks, Tom. I suppose it's the order that trips me up:
starts at 65...
reached a 66...
unexpected at 62...
Maybe you could say a few words on the flow logic.
I suppose it depends on what is meant by "start."
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: stellr@cns.vt.edu, tgl@sss.pgh.pa.us
Subject: Re: unexpected pageaddr
In-Reply-To: <20110202234321.GA22981@cns.vt.edu>
* 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