Re: infinite loop in _bt_getstackbuf - Mailing list pgsql-hackers

From Robert Haas
Subject Re: infinite loop in _bt_getstackbuf
Date
Msg-id CA+TgmobU-hZc-dKWWjeaL4yW2+3gbCUC38F07FW5E8L3X=kU7A@mail.gmail.com
Whole thread Raw
In response to Re: infinite loop in _bt_getstackbuf  (Noah Misch <noah@leadboat.com>)
Responses Re: infinite loop in _bt_getstackbuf
List pgsql-hackers
On Thu, Oct 30, 2014 at 11:45 PM, Noah Misch <noah@leadboat.com> wrote:
>> Given the lack of prior complaints about this
>> loop, I'm not sure I see the need to work harder than that; corruption
>> of this sort must be quite rare.
>
> Looks like _bt_getstackbuf() is always called with some buffer lock held, so
> CHECK_FOR_INTERRUPTS() alone would not help:
>
> http://www.postgresql.org/message-id/flat/16519.1401395152@sss.pgh.pa.us

That's the insert path.  What about the vacuum path?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Mark Woodward
Date:
Subject: CREATE INDEX CONCURRENTLY?
Next
From: Petr Jelinek
Date:
Subject: Re: tracking commit timestamps