Re: PANIC: corrupted item pointer: 32766 - Mailing list pgsql-general

From Igor Neyman
Subject Re: PANIC: corrupted item pointer: 32766
Date
Msg-id F4C27E77F7A33E4CA98C19A9DC6722A205F90917@EXCHANGE.corp.perceptron.com
Whole thread Raw
In response to Re: PANIC: corrupted item pointer: 32766  (Catalin BOIE <cboie-pgsql@66.com>)
Responses Re: PANIC: corrupted item pointer: 32766  (Catalin BOIE <cboie-pgsql@66.com>)
List pgsql-general

> -----Original Message-----
> From: Catalin BOIE [mailto:cboie-pgsql@66.com]
> Sent: Friday, May 14, 2010 5:43 AM
> To: pgsql-general@postgresql.org
> Subject: Re: PANIC: corrupted item pointer: 32766
>
> Some more info.
>
> The PANIC happens several times per minute, so, is really bad for me.
>
> I tried to narrow down based on a field (timestamp) and I
> found some bad "points", but I cannot delete them (same PANIC
> message appear).
>
> Do you have any idea how can I correct that entries?
>
> The worry part is how this happened?!
>
> Thank you!
>
> RAM is 16GiB, 16 "cpus" (including hyperthreading).
>
> On 05/14/2010 09:32 AM, Catalin BOIE wrote:
> > Hello!
> >
> > I have a serious problem with one of my tables.
> >
> > Version: postgresql-server-8.4.3-1.fc12.x86_64
> > Kernel: kernel-2.6.32.11-99.fc12.x86_64
> >
> > I reindexed all indexes on that table, but I still cannot
> workaround
> > this problem.
> >
> > Memory is ECC and the storage is RAID10 (BIOS reported it OK).
> >
> > How I can fix this problem?
> >
> > Thank you!
> >
>
>
> --
> Catalin BOIE
>

If you can read other (good) records from this table, then:

1. create "intermediate table
2. copy all "good" records from original table into the new table
3. drop original table
4. rename "intermediate" table to "original" name
5. re-created required indexes (and any other objects dependent on this
table)


Igor Neyman

pgsql-general by date:

Previous
From:
Date:
Subject: Poor query performance on one of two "like" databases in production.
Next
From: Vick Khera
Date:
Subject: Re: Pulling data from a constraint def