Re: pg_dumpall failure - could not access status of transaction

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