Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 064472E0059 for ; Thu, 24 Apr 2008 14:36:19 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 23406-07 for ; Thu, 24 Apr 2008 14:36:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 6E84B2E0058 for ; Thu, 24 Apr 2008 14:36:15 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m3OHaCaA001287; Thu, 24 Apr 2008 13:36:13 -0400 (EDT) To: "Bhella Paramjeet-PFCW67" cc: pgsql-admin@postgresql.org, "Subbiah Stalin-XCGF84" Subject: Re: Vacuumdb error - corruption In-reply-to: References: <2242.1208477885@sss.pgh.pa.us> Comments: In-reply-to "Bhella Paramjeet-PFCW67" message dated "Thu, 24 Apr 2008 13:12:53 -0400" Date: Thu, 24 Apr 2008 13:36:12 -0400 Message-ID: <1286.1209058572@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/250 X-Sequence-Number: 29014 "Bhella Paramjeet-PFCW67" 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