On Fri, Oct 31, 2014 at 10:29:53AM -0400, Robert Haas wrote: > On Thu, Oct 30, 2014 at 11:45 PM, Noah Misch <n...@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.1401395...@sss.pgh.pa.us > > That's the insert path. What about the vacuum path?
I am not aware of an occasion where the vacuum path will call _bt_getstackbuf() without already holding some buffer lock. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
