Should heap_update/heap_delete hold buffer locks while toasting? - Mailing list pgsql-hackers

From Tom Lane
Subject Should heap_update/heap_delete hold buffer locks while toasting?
Date
Msg-id 6397.978905433@sss.pgh.pa.us
Whole thread Raw
Responses Re: Should heap_update/heap_delete hold buffer locks while toasting?  (Jan Wieck <janwieck@Yahoo.com>)
List pgsql-hackers
The way that heap_update() and heap_delete() are currently coded, they
hold the buffer context lock on the buffer containing the old tuple
while they invoke heap_tuple_toast_attrs().  This strikes me as at least
inefficient and at worst a source of deadlock.  Is it possible to avoid
holding the buffer lock while doing the TOAST manipulations?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: heap_update is broken in current sources
Next
From: Peter Eisentraut
Date:
Subject: Re: CVS regression test failure on OBSD