| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | andy rost <Andy(dot)Rost(at)noaa(dot)gov> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: URGENT - startup process (PID 29541) was terminated by signal 6 |
| Date: | 2006-10-06 19:16:19 |
| Message-ID: | 4724.1160162179@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
andy rost <Andy(dot)Rost(at)noaa(dot)gov> writes:
> Our Opteron DB server had a problem with its RAID controller requiring
> an immediate shutdown of our Postgres server (8.1.3 on FreeBSD 6.0
> release number 10). We used kill -QUIT on the postmaster PID.
> 2006-10-06 12:32:40 CDT PANIC: heap_clean_redo: no block
> ...
> 2006-10-06 12:08:48 CDT PANIC: right sibling is not next child in
> "winddir_idxu"
Um, were you running with full_page_writes off? Bad idea in 8.1 :-( ...
especially on hardware that turns out to not be 100% reliable.
I think your only hope of restarting the database is to use
pg_resetxlog. This is likely to leave you with some database
corruption, in the form of partially applied recent transactions.
I'd recommend a dump and reload, or at least REINDEXing all the
indexes, to forestall problems from that. While you are at it,
update to 8.1.4.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2006-10-06 19:16:53 | Re: Storing images in PostgreSQL databases (again) |
| Previous Message | Ron Johnson | 2006-10-06 19:07:37 | Re: Storing images in PostgreSQL databases (again) |