Skip site navigation (1) Skip section navigation (2)

Should heap_update/heap_delete hold buffer locks while toasting?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Should heap_update/heap_delete hold buffer locks while toasting?
Date: 2001-01-07 22:10:33
Message-ID: 6397.978905433@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: 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

Responses

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group