From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bhella Paramjeet-PFCW67 <PBhella@Motorola.com>
Cc: pgsql-admin@postgresql.org, "Subbiah Stalin-XCGF84" <SSubbiah@Motorola.com>
Subject: Re: Vacuumdb error - corruption
Date: Thu, 24 Apr 2008 13:36:12 -0400
Message-ID: <1286.1209058572@sss.pgh.pa.us> (raw)
In-Reply-To: <C84662912D280D4AB5C50100A100F0C5034E9601@ct11exm61.ds.mot.com>
References: <C84662912D280D4AB5C50100A100F0C5034A6171@ct11exm61.ds.mot.com>
<2242.1208477885@sss.pgh.pa.us>
<C84662912D280D4AB5C50100A100F0C5034E9601@ct11exm61.ds.mot.com>
"Bhella Paramjeet-PFCW67" <PBhella@Motorola.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, PBhella@Motorola.com, SSubbiah@Motorola.com
Subject: Re: Vacuumdb error - corruption
In-Reply-To: <1286.1209058572@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox