Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 424CF9FA3DA for ; Sun, 7 Jan 2007 22:49:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 89880-03 for ; Sun, 7 Jan 2007 22:49:11 -0400 (AST) X-Greylist: delayed 00:23:19.167313 by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 36A4C9FA385 for ; Sun, 7 Jan 2007 22:49:11 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by svr4.postgresql.org (Postfix) with ESMTP id AF2F35AF5CE for ; Mon, 8 Jan 2007 02:25:51 +0000 (GMT) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id F350E6F219 for ; Sun, 7 Jan 2007 21:22:24 -0500 (EST) Received: from web1.messagingengine.com ([10.202.2.210]) by out1.internal (MEProxy); Sun, 07 Jan 2007 21:22:24 -0500 Received: by web1.messagingengine.com (Postfix, from userid 99) id D4011FD88; Sun, 7 Jan 2007 21:22:24 -0500 (EST) Message-Id: <1168222944.2766.283581027@webmail.messagingengine.com> X-Sasl-Enc: sXvdBKIekWGp3Ftqs197hRt4Lj9+BaFICAYpguru2v/d 1168222944 From: "Robert Leftwich" To: pgsql-admin@postgresql.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface Subject: Invalid page header Date: Mon, 08 Jan 2007 13:22:24 +1100 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200701/56 X-Sequence-Number: 24212 Along similar lines to other recent posts I've noticed in the logs some "Invalid page header in block ### of relation ...". errors. Given that we have two basically identical s/w setups (ubuntu 6.06 LTS, PG8.1.4) running on different h/w and only 1 box is reporting these errors and based on the feedback to other similar posts, it looks like a h/w issue. I'd like to hear the lists collective wisdom on what would be the best way to identify what is causing these errors, given that there are no system-level errors being reported. Robert