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:32:22 -0500
Message-ID: <5031.1296689542@sss.pgh.pa.us> (raw)
In-Reply-To: <20110202204651.GA10182@cns.vt.edu>
References: <20110202204651.GA10182@cns.vt.edu>
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
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: <5031.1296689542@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