Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CB718633CE1 for ; Fri, 7 May 2010 11:19:42 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 34934-09 for ; Fri, 7 May 2010 14:19:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 54CF063340A for ; Fri, 7 May 2010 11:19:35 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 07 May 2010 09:19:33 -0500 Message-Id: <4BE3DB1D020000250003138A@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 07 May 2010 09:19:23 -0500 From: "Kevin Grittner" To: "Siddharth Shah" Cc: Subject: Re: ERROR: XX001 (Critical and Urgent) References: <4BE3C93C.70800@elitecore.com> <4BE3D0EF020000250003137D@gw.wicourts.gov> <4BE41AE1.4010804@elitecore.com> In-Reply-To: <4BE41AE1.4010804@elitecore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201005/92 X-Sequence-Number: 34565 [rearranged to put the most critical point first] Siddharth Shah wrote: > I don't have any backup available, Is there any way to fix this ? I *strongly* recommend that you shut down the database and take a file copy of the whole data tree (everything under what -D points to on the server startup) which you should keep until long after you think everything is working OK again. Before you do anything else. You are at risk of losing everything in the database, and one misstep could put you over the edge. If this is a production database, tell the users that it is down until further notice. > What can be the method to verify that it's a database corruption ? > ERROR: index "pg_class_relname_nsp_index" contains unexpected > zero page at block 33 Getting an error like that indicates database corruption. > HINT: Please REINDEX it. > xdb=# reindex index pg_class_relname_nsp_index; > > Now INDEXing taking High CPU and postgres baffled. That is an index on the table which describes all your tables and indexes. It normally doesn't take a long time to reindex. You should consider doing your recovery in single-user mode (*AFTER* you make that copy): http://www.postgresql.org/docs/8.4/interactive/app-postgres.html After trying reindex in that context, please post again. -Kevin