Steven Rosenstein <[EMAIL PROTECTED]> writes:
> Any idea why Postgres would be looking for a clog file name 0FC0 when the
> most recent filename is 04CE?
Corrupt data --- specifically a bad transaction number in a tuple
header. (In practice, this is the first field looked at in which
we can read
Postgres V7.3.9-2.
While executing a query in psql, the following error was generated:
vsa=# select * from vsa.dtbl_logged_event_20050318 where id=2689472;
PANIC: open of /vsa/db/pg_clog/0FC0 failed: No such file or directory
server closed the connection unexpectedly
This probably me
