On Fri, Nov 20, 2009 at 4:03 PM, Tom Lane wrote:
> Scott Marlowe writes:
>> 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.
>
> Do you mean you
Scott Marlowe writes:
> 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.
Do you mean you actually have fillfactor set somewhere? It didn't show
o
On Fri, Nov 20, 2009 at 3:15 PM, Tom Lane wrote:
> Scott Marlowe 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 s
Scott Marlowe 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 be
On Fri, Nov 20, 2009 at 2:33 PM, Tom Lane wrote:
> Scott Marlowe 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"
>
> Huh. Don't suppose you can extract a reproducible test case ;-).
> Wh
Scott Marlowe 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"
Huh. Don't suppose you can extract a reproducible test case ;-).
What are the exact definitions of the table and index?
