On Wed, Feb 02, 2011 at 06:32:22PM -0500, Tom Lane wrote: > Ray Stell <stellr@xxxxxxxxxx> 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." -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
