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

Responses

• Re: Should heap_update/heap_delete hold buffer locks while toasting? at 2001-01-08 18:37:04 from Jan Wieck

pgsql-hackers by date

Next:	From: Emmanuel Charpentier	Date: 2001-01-07 22:18:39
	Subject: Re: A post-7.1 wish-list.
Previous:	From: Emmanuel Charpentier	Date: 2001-01-07 22:10:30
	Subject: Re: A post-7.1 wish-list.