Re: pg_dumpall failure - could not access status of transaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert Leftwich" <pg(at)rtl(dot)fmailbox(dot)com>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dumpall failure - could not access status of transaction
Date: 2007-02-03 03:28:42
Message-ID: 26856.1170473322@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Robert Leftwich" <pg(at)rtl(dot)fmailbox(dot)com> writes:
> On Fri, 02 Feb 2007 21:21:47 -0500, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> said:
>> Also, can you show us the pg_filedump output for the page of
>> pg_description you think is trashed? I find "-i -f" options give
>> the most useful output usually.

> [ dump snipped ]

Yeah, the last part of that page has been trashed --- mostly zeroes, but
there's a bit with an odd data pattern that doesn't make much sense to
me:

> 1a3c: d09b3000 b89b3000 a09b3000 889b3000 ..0...0...0...0.
> 1a4c: 709b3000 589b3000 409b3000 289b3000 p(dot)0(dot)X(dot)0(dot)(at)(dot)0(dot)(.0.
> 1a5c: 109b3000 f89a3000 e09a3000 c89a3000 ..0...0...0...0.
> 1a6c: b09a3000 989a3000 809a3000 689a3000 ..0...0...0.h.0.

This seems like it could indicate either a hardware or operating-system
flake-out. Have you tried running hardware diagnostic tests on the
machine?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Robert Leftwich 2007-02-03 03:49:54 Re: pg_dumpall failure - could not access status of transaction
Previous Message Robert Leftwich 2007-02-03 03:09:33 Re: pg_dumpall failure - could not access status of transaction