pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Siddharth Shah <siddharth.shah@elitecore.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: ERROR:  XX001 (Critical and Urgent)
Date: Fri, 07 May 2010 09:19:23 -0500
Message-ID: <4BE3DB1D020000250003138A@gw.wicourts.gov> (raw)
In-Reply-To: <4BE41AE1.4010804@elitecore.com>
References: <4BE3C93C.70800@elitecore.com>
	<4BE3D0EF020000250003137D@gw.wicourts.gov>
	<4BE41AE1.4010804@elitecore.com>

[rearranged to put the most critical point first]
 
Siddharth Shah <siddharth.shah@elitecore.com> 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



view thread (9+ messages)  latest in thread

Message-ID: <4BE3DB1D020000250003138A@gw.wicourts.gov>
Permalink:  ../4BE3DB1D020000250003138A@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4BE3DB1D020000250003138A@gw.wicourts.gov

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, siddharth.shah@elitecore.com
  Subject: Re: ERROR:  XX001 (Critical and Urgent)
  In-Reply-To: <4BE3DB1D020000250003138A@gw.wicourts.gov>
  References: <4BE3C93C.70800@elitecore.com> <4BE3D0EF020000250003137D@gw.wicourts.gov> <4BE41AE1.4010804@elitecore.com> <4BE3DB1D020000250003138A@gw.wicourts.gov>

* 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