Re: panic failed to add item

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: panic failed to add item
Date: 2009-11-20 22:19:26
Message-ID: dcc563d10911201419l7b994e7awa4ccc5e003f8f5aa@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Nov 20, 2009 at 3:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
>>>> I get this running mnogosearch against my 8.4.1 database consistently:
>>>> PANIC:  failed to add item to the right sibling in index "logged_in_uid"
>
> Hmm, if uid is an integer then all the index entries will be the same
> size, which eliminates my first theory about there being some corner
> case where we're (still) choosing an infeasible split point.  Can you
> comment about the insertion pattern for uid's --- are they ever-increasing
> for instance?  Do you have any special properties such as fillfactor set
> on that index?

Access is pretty random actually, and fill factor on this database is
100% because it doesn't really get updated, just appended to. There
are a lot of parallel insertions going on if that helps.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-11-20 23:03:09 Re: panic failed to add item
Previous Message Tom Lane 2009-11-20 22:15:47 Re: panic failed to add item