Thread: PANIC: right sibling

PANIC: right sibling

From
"Scott Whitney"
Date:
I don't really understand the postings I've found on this issue. This has
been going on for quite some time, but now that I'm regularly vacuuming this
db, I was looking for any info on how to fix this problem...I don't even
know enough about it to know what to include in this message.


This is the last output of:

vacuumdb -f -z -v rt3



vacuumdb: vacuuming of database "rt3" failed: PANIC:  right sibling is not
next child in "tickets1"
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.


Re: PANIC: right sibling

From
Kenneth Marshall
Date:
You have a corrupt index, run:

REINDEX INDEX tickets1;

Ken

On Tue, Dec 04, 2007 at 11:03:15AM -0600, Scott Whitney wrote:
> I don't really understand the postings I've found on this issue. This has
> been going on for quite some time, but now that I'm regularly vacuuming this
> db, I was looking for any info on how to fix this problem...I don't even
> know enough about it to know what to include in this message.
>
>
> This is the last output of:
>
> vacuumdb -f -z -v rt3
>
>
>
> vacuumdb: vacuuming of database "rt3" failed: PANIC:  right sibling is not
> next child in "tickets1"
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
>                 http://www.postgresql.org/about/donate
>

Re: PANIC: right sibling

From
Alvaro Herrera
Date:
Scott Whitney wrote:
> I don't really understand the postings I've found on this issue. This has
> been going on for quite some time, but now that I'm regularly vacuuming this
> db, I was looking for any info on how to fix this problem...I don't even
> know enough about it to know what to include in this message.

Probably a REINDEX on the corrupted index would solve it.

I'm not sure if there's a known bug in the version you're using.  If
there is, obviously you should upgrade to a fixed one.  Otherwise you
may be able to help us find it by saving the corrupted index before
reindexing it, for examination.

--
Alvaro Herrera                          Developer, http://www.PostgreSQL.org/
"The only difference is that Saddam would kill you on private, where the
Americans will kill you in public" (Mohammad Saleh, 39, a building contractor)