error opening pg_clog file

From: Steve Wolfe <nw(at)codon(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: error opening pg_clog file
Date: 2004-10-12 22:29:27
Message-ID: 416C5AC7.9030403@codon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Saturday, our database machine locked up hard on us due to some
faulty hardware. Since then, we have been getting messages like this:

ERROR: could not access status of transaction 143934068
DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0089": No
such file or directory

Looking in /usr/local/pgsql/data/pg_clog, the "0089" file isn't
there. Some investigation revealed these messages:

http://archives.postgresql.org/pgsql-hackers/2004-01/msg00534.php
http://www.mail-archive.com/pgsql-admin(at)postgresql(dot)org/msg13874.html

So, I did "dd if=/dev/zero of=/usr/local/pgsql/data/pg_clog/0089
bs=8k count=1". I did an ls to verify that the file existed. I started
the postmaster back up, tried a VACUUM, and got:

vacuumdb: vacuuming of database "hyperseek" failed: ERROR: could not
access status of transaction 144565028
DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0089": No
such file or directory

I looked, and the "0089" file was gone again. Is there anything I
can do to save the situation? (The PG version is 7.4.2)

steve wolfe

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ted Shab 2004-10-12 22:48:41 LISTEN/NOTIFY for lightweight replication
Previous Message Tom Lane 2004-10-12 22:27:44 Re: deadlock with vacuum full on 7.4.5