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

Re: ERROR: could not access status of transaction 210

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Cain <cain(at)cshl(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: could not access status of transaction 210
Date: 2004-11-29 17:57:06
Message-ID: 19965.1101751026@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Scott Cain <cain(at)cshl(dot)org> writes:
> After dropping a database, recreating it and trying to add a table to
> it, I am getting this message:

> ERROR:  could not access status of transaction 210
> DETAIL:  could not open file "/opt/postgres/data/pg_clog/0000": No such file or directory

> There is a file call 0001 in pg_clog, but not 0000.  This is a
> relatively new install of PostgreSQL 7.4.6 built from source on a
> similarly new install of Fedora Core 3.

Hmm, are you sure it's 7.4.6 and has been 7.4.6 for the whole existence
of the data directory?  This looks like a hint-bit-drop problem, which
I thought we had fixed the last of as of 7.4.6.

> So, what can I do to get rid of this?  I already dropped the database
> (which I can do successfully) and created an empty database in its
> place, but I can't add any tables to it.  Also, when I do a '\dt' in
> that empty database, I get a similar message:

Apparently you've got hint-bit corruption in template1.  I'd recommend a
fresh initdb.  If you're desperate to avoid that because you have other
databases that aren't broken, you could reconstruct template1 from
template0 (see techdocs.postgresql.org for the procedural details).

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Scott CainDate: 2004-11-29 18:01:54
Subject: Re: ERROR: could not access status of transaction 210
Previous:From: Scott CainDate: 2004-11-29 17:00:03
Subject: ERROR: could not access status of transaction 210

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