On 05/14/2010 08:49 PM, Igor Neyman wrote:
>
>
>> -Original Message-
>> From: Catalin BOIE [mailto:cboie-pg...@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 hap
On 05/14/2010 07:16 PM, Emanuel Calvo Franco wrote:
>> 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 h
Excerpts from Catalin BOIE's message of vie may 14 02:32:01 -0400 2010:
> 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
Hmm, it's pretty unfortunate that those buffer checks are inside
PageR
> -Original Message-
> From: Catalin BOIE [mailto:cboie-pg...@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 m
> 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 t
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 h
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
