I am attempting to get a handle on the corruption that caused
the following error:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: could not access status of
transaction 3183024
DETAIL: could not open file pg_clog/0003: No such file or directory
pg_dump: The command was:
I wrote:
I am attempting to get a handle on the corruption that caused
the following error...
After a bit more digging I found a couple of old messages that helped -
http://archives.postgresql.org/pgsql-admin/2004-01/msg00258.php
The last tuple that is valid is (3, 123) and looking at record 3
Along similar lines to other recent posts I've noticed in the logs some
Invalid page header in block ### of relation errors. Given that
we have two basically identical s/w setups (ubuntu 6.06 LTS, PG8.1.4)
running on different h/w and only 1 box is reporting these errors and
based on the
