Skip site navigation (1) Skip section navigation (2)

Re: CRITICAL HELP NEEDED! DEAD DB!

From: Cott Lang <cott(at)internetstaff(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CRITICAL HELP NEEDED! DEAD DB!
Date: 2004-09-24 19:18:00
Message-ID: 1096053480.3554.8.camel@localhost (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 2004-09-24 at 11:43, Tom Lane wrote:
> 
> I think your only chance is pg_resetxlog.  Be aware that you won't
> necessarily have a consistent database afterwards --- in particular,
> whichever index that failure is about is certainly broken.  I'd
> recommend a dump and reload, plus as much manual verification of data
> consistency as you can manage.

That's what I've done, so far so good, although we are still checking
consistency against the last backup.  Thanks for the info. Luckily this
was one of our smaller databases ...

> How did you get into this state, anyway?

I wish I knew - this is what appeared to start it:

Sep 24 10:19:41 snafu postgres[18176]: [464-1] ERROR:  could not open
segment 1 of relation "idx_ordl_id" (target block 1719234412): No such
file or
Sep 24 10:19:41 snafu postgres[18176]: [464-2]  directory

I can't figure out what the exact problem is; there were no I/O errors
or any other relative messages at the time, the box was empty, and
nothing remarkable was going on.  :(

thanks,
Cott

PS: No, I don't think it's a PG problem. :)





In response to

Responses

pgsql-hackers by date

Next:From: Cott LangDate: 2004-09-24 19:20:50
Subject: Re: CRITICAL HELP NEEDED! DEAD DB!
Previous:From: Tom LaneDate: 2004-09-24 18:43:22
Subject: Re: CRITICAL HELP NEEDED! DEAD DB!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group