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

Re: Missing pg_clog file / corrupt index / invalid page header

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: alex <an(at)clickware(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Missing pg_clog file / corrupt index / invalid page header
Date: 2007-09-05 07:02:11
Message-ID: 2394.1188975731@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
alex <an(at)clickware(dot)de> writes:
> Summary
> ==========

> Various errors like:
> "invalid page header in block 8658 of relation",
> "could not open segment 2 of relation 1663/77142409/266753945 (target 
> block 809775152)",
> "ERROR:  could not access status of transaction 2134240 DETAIL:  could 
> not open file "pg_clog/0002": File not found",
> "CEST PANIC:  right sibling's left-link doesn't match"

Ick.  For any one of those errors, I would've thought it was Postgres'
fault, but when you have several it's not so clear.  Kernel or hardware
flakiness have to be considered as alternative explanations.

> on the following system:
> Postgres 8.1.8
> SUsE Linux Kernel 2.6.13-15.8-smp

2.6.13 is not the latest, nor even close --- can you update the kernel
and see if things get better?

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2007-09-05 08:32:18
Subject: Re: BUG #3595: Segmentation fault with a simple select query
Previous:From: alexDate: 2007-09-05 06:18:31
Subject: Missing pg_clog file / corrupt index / invalid page header

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