Re: CRITICAL HELP NEEDED! DEAD DB!
От | Cott Lang |
---|---|
Тема | Re: CRITICAL HELP NEEDED! DEAD DB! |
Дата | |
Msg-id | 1096053480.3554.8.camel@localhost обсуждение исходный текст |
Ответ на | Re: CRITICAL HELP NEEDED! DEAD DB! (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: CRITICAL HELP NEEDED! DEAD DB!
|
Список | 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. :)
В списке pgsql-hackers по дате отправления: