Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0218A9F993D for ; Mon, 8 Oct 2007 01:52:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 64951-09 for ; Mon, 8 Oct 2007 01:52:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 32EAB9F992C for ; Mon, 8 Oct 2007 01:52:37 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l984qZBR028714; Mon, 8 Oct 2007 00:52:35 -0400 (EDT) To: "Mike C" cc: pgsql-admin@postgresql.org Subject: Re: Database Recovery In-reply-to: References: <26143.1191808096@sss.pgh.pa.us> Comments: In-reply-to "Mike C" message dated "Mon, 08 Oct 2007 14:58:28 +1300" Date: Mon, 08 Oct 2007 00:52:35 -0400 Message-ID: <28713.1191819155@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/45 X-Sequence-Number: 26959 "Mike C" writes: > On 10/8/07, Tom Lane 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