From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Ray Stell
Sent: 02 February 2011 20:47
To: pgsql-admin@postgresql.org
Subject: [ADMIN] unexpected pageaddr
Streaming replication standby moved from 9.0.2->9.0.3 logs this up
startup:
database system was s
Ray Stell 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
>> c
On Wed, Feb 02, 2011 at 06:32:22PM -0500, Tom Lane wrote:
> Ray Stell 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
Ray Stell 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/6600
> unexpected pageadd
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/6600
unexpected pageaddr 0/6200 in log file 0, segme
