Re: BUG #3302: Crash on gist ltree - PANIC: failed to add item to index page

From: Cstdenis <cstdenis(at)ctgameinfo(dot)com>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3302: Crash on gist ltree - PANIC: failed to add item to index page
Date: 2007-05-24 14:37:43
Message-ID: 4655A337.7020108@ctgameinfo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Teodor Sigaev wrote:
>
>> CREATE INDEX idx_picture_comments_id_tree_gist
>> ON picture_comments
>> USING gist
>> (id_tree);
>>
>> and the server exited on signal 6 (core dumped)
>
> Is it reproducible? Pls, send to me dump of ltree column.

I haven't been able to reproduce it. I think its a race condition
between some of the other processes running at the time. I'm not sure
what else was running on it, but the error suggests an insert to me and
there may have been a vacuum running (plus there are always plenty of
selects running).

It is not reasonable for me to send you an ltree dump since the talbe is
about 2 million rows, but I'll send a small sample and describe it.

The ltree is a tree is id numbers of rows (the table is a linked list of
comments and their replies (think slashdot's comment system) the id
numbers come from a serial and are in most cases 1-2 levels deep.

Here is a sample tho not entirely representative because all very old
entries have no replies (its a newer feature) and are therefore one
level deep.

"1821086"
"1819309"
"1817475"
"1810945"
"1810929"
"1810913"
"1808878"
"1795503"
"1792553"
"1792753"
"1792229"
"1788609"
"1787736"
"1775321"
"1775175"
"1775231"
"1773624"
"1768493"
"1767839"
"116026.116028.116032"
"116021.116048"
"111129.116063"
"116093.116094"
"116095.116100"
"116101.116104"
"116101.116104.116106"
"116101.116104.116106.116114.116117"
"116093.116094.116096.116122"
"116119.116123"
"116120.116126"
"116093.116094.116096.116103.116127"
"116128.116130"
"116101.116104.116106.116114.116117.116121.116131"
"116101.116104.116106.116114.116117.116121.116131.116136"
"116138.116143"
"116135.116146"
"116138.116143.116148"
"115343.115661.116152"
"116163.116166"
"116168.116171"
"116173.116174.116175.116176.116177"
"116173.116174.116175.116176.116177.116178"
"116179.116188.116191"
"116190.116192"
"116190.116192.116198.116199"
"116190.116192.116198.116199.116200"
"116132.116144"
"116244.116246"
"116249.116251"
"116155.116280"
"116279.116291"
"116260.116297"
"116279.116298"
"116257.116259.116262.116300"
"116303.116306"
"116308.116310"
"116308.116310.116312"
"116320.116321"
"116319.116322"
"116320.116321.116324"
"116333.116335"
"116342.116347"
"116343.116353"
"116359.116360"

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-05-24 15:27:49 Re: BUG #3301: explain crashes server on simple (?) query
Previous Message Magnus Hagander 2007-05-24 14:35:33 Re: BUG #3304: win32 build fails, because of wrong include