"Mike C" <smith.not.western@gmail.com> writes: > I have a corrupt database. I copied the database directory offsite and > restored from a backup. I'm now trying to recover data in the corrupt > database added since the last backup. Any advice on how to approach > this? If you're lucky, REINDEX might solve your problems. The messages you showed are all about index corruption, which REINDEX can fix. If you've got corruption in the tables themselves then you might be screwed, but try reindexing and see what happens ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster

"Mike C" <smith.not.western@gmail.com> writes: > On 10/8/07, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> If you're lucky, REINDEX might solve your problems. > My problem is that I can't even start postmaster to perform the > reindex on now. As soon as I try start (via pg_ctl, 8.1.10): > ... > postgres_report[24165]: [9-1] LOG: redo done at 520/6E2D100 > postgres_report[24165]: [10-1] PANIC: failed to re-find parent key > in "24977" for split pages 230790/263989 Ugh, so that's happening during recovery cleanup. Sucks to be you :-( You should try pg_resetxlog, then start the database and reindex, but I'm not holding out a lot of hope here. It sounds like the SAN failure messed things up beyond recovery. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate