Re: BUG #3567: invalid page header in block XXXXof relation - Mailing list pgsql-bugs

From Zdenek Kotala
Subject Re: BUG #3567: invalid page header in block XXXXof relation
Date
Msg-id 46CD4B72.2000304@sun.com
Whole thread Raw
In response to Re: BUG #3567: invalid page header in block XXXXof relation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> "sapna kapoor" <sapna.kapoor@nic.in> writes:
>> some tables are giving error :
>> ERROR:  invalid page header in block 32655 of relation "AAAA" while
>> accessing.
>
>> Some are giving
>> ERROR:  could not access status of transaction 1778384896
>> DETAIL:  could not open file "pg_clog/06A0": No such file or directory
>
> If you had just one of these, I might think it suggested a software
> problem.

The similar clog problem was reported there
http://archives.postgresql.org/pgsql-bugs/2007-07/msg00124.php.

It looks like vacuum truncate clog file but, some tuples still have xmin or xmax
from truncated clog.

Sapna,

can
You try following http://pgfoundry.org/projects/pgcheck/ project. It is still in
alpha, but page check
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgcheck/pokus/pgcheck_page/) should
be work.

        Zdenek

pgsql-bugs by date:

Previous
From: Russell Smith
Date:
Subject: Re: BUG #3563: DATESTYLE feature suggestion
Next
From: "Marko Kreen"
Date:
Subject: Re: BUG #3571: call to decrypt causes segfault