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 fee
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
On Fri, 02 Feb 2007 21:21:47 -0500, "Tom Lane" <[EMAIL PROTECTED]> said:
>
> Yeah. What file names are actually present in $PGDATA/pg_clog/, and
> what does pg_controldata say about the current XID counter? We have
> seen some bugs where clog files get deleted before they're not needed
> anymor
On Fri, 02 Feb 2007 22:28:42 -0500, "Tom Lane" <[EMAIL PROTECTED]> said:
> This seems like it could indicate either a hardware or operating-system
> flake-out. Have you tried running hardware diagnostic tests on the
> machine?
>
A couple of weeks back when it had 'invalid page header' problems,
