From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Gerd König <koenig(at)transporeon(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org>, pgpool-general(at)pgfoundry(dot)org |
Subject: | Re: panic: index siblings mismatch |
Date: | 2009-03-10 23:22:46 |
Message-ID: | dcc563d10903101622g5afe065er54c78b047dc74608@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 10, 2009 at 3:35 PM, Gerd König <koenig(at)transporeon(dot)com> wrote:
> Hello,
>
> today I recognized an error while playing with pgpool-II 2.1 and
> postgresql 8.3.5 (on 64bit linux).
> I really don't know if the error is caused by pgpool or if it's
> postgresql-related...?!?
> any hints are much appreciated, since we don't know what happened...
>
> thanks in advance...::GERD::...
>
> a) postgresql log of second db node where the error occured
> b) pgpool log
>
> a)
> ==================================================================
> 2009-03-10 11:16:33 CET [11008]: [1-1] PANIC: right sibling's left-link
> doesn't match: block 695 links to 785 instead of expected 694 in index
> "PartyAddress_index"
This is a sign of index corruption. Have you had any unexpected power
outages lately? you could try reindexing the table that's affected
and see if the problem goes away, but I'd be far more worried about
what caused the original corruption to the index.
From | Date | Subject | |
---|---|---|---|
Next Message | Piotre Ugrumov | 2009-03-10 23:36:36 | Re: Enable user access from remote host |
Previous Message | Kevin Grittner | 2009-03-10 21:47:21 | tsearch2 dictionary for statute cites |