| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mike C" <smith(dot)not(dot)western(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Database Recovery |
| Date: | 2007-10-08 04:52:35 |
| Message-ID: | 28713.1191819155@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Mike C" <smith(dot)not(dot)western(at)gmail(dot)com> writes:
> On 10/8/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Malm Paul | 2007-10-08 06:29:24 | Installing postgreSQL |
| Previous Message | Scott Marlowe | 2007-10-08 03:07:00 | Re: Warm/hot backup server question |