pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Robert Leftwich <pg@rtl.fmailbox.com>
To: pgsql-admin@postgresql.org
Subject: Re: pg_dumpall failure - could not access status of transaction
Date: Sat, 03 Feb 2007 11:36:18 +1100
Message-ID: <1170462978.22675.1172672723@webmail.messagingengine.com> (raw)
In-Reply-To: <1170455123.6719.1172656201@webmail.messagingengine.com>
References: <1170455123.6719.1172656201@webmail.messagingengine.com>

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





view thread (7+ messages)  latest in thread

Message-ID: <1170462978.22675.1172672723@webmail.messagingengine.com>
Permalink:  ../1170462978.22675.1172672723@webmail.messagingengine.com/
Also on:    postgresql.org/message-id/1170462978.22675.1172672723@webmail.messagingengine.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pg@rtl.fmailbox.com
  Subject: Re: pg_dumpall failure - could not access status of transaction
  In-Reply-To: <1170462978.22675.1172672723@webmail.messagingengine.com>
  References: <1170455123.6719.1172656201@webmail.messagingengine.com> <1170462978.22675.1172672723@webmail.messagingengine.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox