| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Henka" <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-21 15:40:44 |
| Message-ID: | 17074.1182440444@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Henka" <henka(at)cityweb(dot)co(dot)za> writes:
> I happened to notice this error in the log when my application was refused
> a db connection (quite unexpectedly):
> PANIC: corrupted item pointer: offset = 3308, size = 28
> LOG: autovacuum process (PID 18165) was terminated by signal 6
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 concur with the other comments that a crash with fsync off might well
have allowed more corruption than just this to sneak in, though :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | danmcb | 2007-06-21 16:28:42 | finding items with 0 rels for a 0 to many relationship |
| Previous Message | Andrew Sullivan | 2007-06-21 15:39:16 | Re: Experiences of PostgreSQL on-disk bitmap index patch |