Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id F3C4C1337B90 for ; Wed, 2 Feb 2011 19:32:30 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 42864-04 for ; Wed, 2 Feb 2011 23:32:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 7B9751337B8D for ; Wed, 2 Feb 2011 19:32:23 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p12NWMrG005032; Wed, 2 Feb 2011 18:32:22 -0500 (EST) To: Ray Stell cc: pgsql-admin@postgresql.org Subject: Re: unexpected pageaddr In-reply-to: <20110202204651.GA10182@cns.vt.edu> References: <20110202204651.GA10182@cns.vt.edu> Comments: In-reply-to Ray Stell message dated "Wed, 02 Feb 2011 15:46:51 -0500" Date: Wed, 02 Feb 2011 18:32:22 -0500 Message-ID: <5031.1296689542@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201102/4 X-Sequence-Number: 36643 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/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