Skip site navigation (1) Skip section navigation (2)

Re: BUG #3567: invalid page header in block XXXXof relation

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: sapna kapoor <sapna(dot)kapoor(at)nic(dot)in>, pgsql-bugs(at)postgresql(dot)org, Robert Mach <mach(dot)robert(at)gmail(dot)com>
Subject: Re: BUG #3567: invalid page header in block XXXXof relation
Date: 2007-08-23 08:55:14
Message-ID: 46CD4B72.2000304@sun.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> "sapna kapoor" <sapna(dot)kapoor(at)nic(dot)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

In response to

pgsql-bugs by date

Next:From: Dave PageDate: 2007-08-23 11:30:29
Subject: Cannot create a type in pg_catalog
Previous:From: Marko KreenDate: 2007-08-23 08:54:58
Subject: Re: BUG #3571: call to decrypt causes segfault

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group