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
Robert Leftwich wrote:
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
If your database system has already experienced on the order of 3183024
transactions, then you should wonder
Robert Leftwich [EMAIL PROTECTED] writes:
On Fri, 02 Feb 2007 21:21:47 -0500, Tom Lane [EMAIL PROTECTED] said:
Also, can you show us the pg_filedump output for the page of
pg_description you think is trashed? I find -i -f options give
the most useful output usually.
[ dump snipped ]
Yeah,
