Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 603F61336FA7 for ; Wed, 2 Feb 2011 16:46:59 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 47248-04 for ; Wed, 2 Feb 2011 20:46:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by mail.postgresql.org (Postfix) with ESMTP id BC45D133616B for ; Wed, 2 Feb 2011 16:46:51 -0400 (AST) Received: by locust.cns.vt.edu (Postfix, from userid 986) id 44557118DD3; Wed, 2 Feb 2011 15:46:51 -0500 (EST) Date: Wed, 2 Feb 2011 15:46:51 -0500 From: Ray Stell To: pgsql-admin@postgresql.org Subject: unexpected pageaddr Message-ID: <20110202204651.GA10182@cns.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) 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/3 X-Sequence-Number: 36642 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?