From: | Zoltan Boszormenyi <zb(at)cybertec(dot)at> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Heavily fragmented table and index data in 8.0.3 |
Date: | 2008-06-12 15:31:37 |
Message-ID: | 48514159.80609@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane írta:
> Zoltan Boszormenyi <zb(at)cybertec(dot)at> writes:
>
>> The realtime trace I captured from the hung INSERT shows that it
>> enters two functions repeatedly: _bt_relandgetbuf() and _bt_compare().
>> The pattern in which these functions entered match either _bt_moveright() or
>> _bt_insertonpg().
>>
>
> What that sounds like to me is a corrupt index (infinite loop of
> right-links, perhaps). Have you tried REINDEXing the table?
>
> regards, tom lane
>
No, TRUNCATE was faster because there were no live records in the table.
How can such an infinite loop sneak into an index?
Hardware is from Sun, not a grocery store PC, so I don't suppose it to
be faulty.
Is there anything in the 8.0.x series that fixes this (or a similar) bug?
If I could point to something in the release notes, I may get them to
upgrade
and they may upgrade to a newer generation even.
Thanks.
--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
http://www.postgresql.at/
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2008-06-12 15:56:28 | Re: Heavily fragmented table and index data in 8.0.3 |
Previous Message | Tom Lane | 2008-06-12 15:29:56 | Re: Fw: postgrepsql vacuum |