"Bhella Paramjeet-PFCW67" <[EMAIL PROTECTED]> writes:
> Error in the database vacuum log.
> INFO: vacuuming "public.securityevent"
> WARNING: relation "securityevent" TID 21/3: OID is invalid
That smells like a data corruption problem ...
> vacuumdb: vacuuming of database "ectest" failed: ERROR: could not
> access status of transaction 33554431
and so does that, particularly since the value equates to hex 01FFFFFF.
It's a lot easier to believe a hardware-ish fault stuffing such a value
than a software bug.
> Here are the machine specifics on which this database is running:
> Platform: Linux x86_64
> OS: Red Hat Enterprise Linux ES release 4 Kernel version: 2.6.9-34
If I'm reading the Red Hat CVS correctly, that kernel is two years old
next week. Perhaps a newer kernel would help your problems. A quick
troll through the changelog reveals a number of x86_64-specific fixes
that sound like they could have resulted in userspace data corruption.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
