| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Edson <cheighlund(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Panic error on attempted update |
| Date: | 2007-07-12 17:16:50 |
| Message-ID: | 23552.1184260610@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andrew Edson <cheighlund(at)yahoo(dot)com> writes:
> PANIC: right sibling's left-link doesn't match
> Any clue what's causing the panic message to occur?
Corrupt btree index. If you can determine which table is being
inserted/updated when this happens (admittedly the message is not being
helpful), REINDEX should fix it.
Did you have a system crash before this started?
Running something newer than 8.1.4 would be advisable anyway. I seem to
recall that we fixed at least one bug that could produce this symptom,
though I don't see anything specifically about it in the 8.1 CVS logs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Arai | 2007-07-12 17:20:42 | Re: Big table with UNION ALL or partitioning with Tsearch2 |
| Previous Message | imageguy | 2007-07-12 17:07:36 | Updates/Changes to a database |