From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Henk - CityWEB <henka(at)cityweb(dot)co(dot)za> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 8.2.3 PANIC with "corrupted item pointer" |
Date: | 2007-06-22 20:29:07 |
Message-ID: | 26204.1182544147@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Henk - CityWEB <henka(at)cityweb(dot)co(dot)za> writes:
> On Thu, 21 Jun 2007, Tom Lane wrote:
>> FWIW, the only occurrences of that specific message text are in
>> PageIndexTupleDelete and PageIndexMultiDelete, so you can be pretty sure
>> that this is just a corrupted-index problem. Once you've identified
>> which table has the problem, a REINDEX should fix it.
> I've identified the offending index, but REINDEX also causes the PANIC.
> I also tried DROPping the index (and REINDEX DATABASE foo), but that too
> causes a panic.
In that case you've not correctly identified the broken index. It
sounds to me like the problem could possibly be in a system catalog
index. REINDEX SYSTEM with use of system indexes disabled might help
(see the REINDEX man page).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-06-22 20:38:12 | Re: Establishing a primary key |
Previous Message | Henk - CityWEB | 2007-06-22 20:16:00 | Re: 8.2.3 PANIC with "corrupted item pointer" |