Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 434E69FB2F8 for ; Fri, 2 Feb 2007 20:36:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 18641-07 for ; Fri, 2 Feb 2007 20:36:09 -0400 (AST) X-Greylist: delayed 02:10:46.739095 by SQLgrey-1.7.4 Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by postgresql.org (Postfix) with ESMTP id 222349FB2DC for ; Fri, 2 Feb 2007 20:36:20 -0400 (AST) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id A94609E680 for ; Fri, 2 Feb 2007 19:36:18 -0500 (EST) Received: from web4.messagingengine.com ([10.202.2.213]) by out1.internal (MEProxy); Fri, 02 Feb 2007 19:36:18 -0500 Received: by web4.messagingengine.com (Postfix, from userid 99) id 63AC717928C; Fri, 2 Feb 2007 19:36:18 -0500 (EST) Message-Id: <1170462978.22675.1172672723@webmail.messagingengine.com> X-Sasl-Enc: ynBEl52utnwSVzgjZQ5K38SHuv97PfhrxJrFYn4nUPoS 1170462978 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 References: <1170455123.6719.1172656201@webmail.messagingengine.com> Subject: Re: pg_dumpall failure - could not access status of transaction In-Reply-To: <1170455123.6719.1172656201@webmail.messagingengine.com> Date: Sat, 03 Feb 2007 11:36:18 +1100 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/34 X-Sequence-Number: 24499 I wrote: > I am attempting to get a handle on the corruption that caused > the following error... After a bit more digging I found a couple of old messages that helped - http://archives.postgresql.org/pgsql-admin/2004-01/msg00258.php The last tuple that is valid is (3, 123) and looking at record 3 in the corresponding file, it appears to be the last entry in that record and it has no errors. Assuming that the next tuple will be in record 4 and dumping it, results in the first 32 items having the error "Error: Computed header length not equal to header size. Computed <28> Header: <0>" or similar. Is there any likelihood this is a pg problem (it is running 8.1.4 on ubuntu 6.06 server)? Is upgrading to 8.2.x worthwhile or is it more likely to be a h/w issue? Note that the same box had 'invalid page header' issues around 4 weeks ago - although these have not occurred since the supplier replaced the shared memory video card with a non-shared card 2 weeks ago. Basically, it would be good to be able to go to the supplier and say there is definitely a h/w issue here, so any help in this area would be great. Thanks Robert