Re: ClusterDB error message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cgg007(at)yahoo(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: ClusterDB error message
Date: 2005-11-10 16:51:42
Message-ID: 9863.1131641502@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

CG <cgg007(at)yahoo(dot)com> writes:
> Can anyone surmise what this message is really saying?

> clusterdb: clustering of table "letter" in database "addata" failed: ERROR:
> could not access status of transaction 1696665057
> DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0652": No such file or directory

This is a corrupt-data problem: the xmin or xmax field of a row header
has been overwritten with garbage. (Very likely, more than that has
been overwritten, but xmin/xmax is usually the first thing looked at
so this is the typical symptom.)

See the PG list archives for prior discussions of how to isolate and get
rid of corrupted rows.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2005-11-10 16:54:51 Re: Partitioning in 8.1
Previous Message Chris Hoover 2005-11-10 16:34:08 Partitioning in 8.1