Use the standard lock manager to establish priority order when there

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 93b24772782e7518dee2f85366aa7a80a2beb937
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2005-04-30T19:03:33Z
Releases: 8.1.0
Use the standard lock manager to establish priority order when there
is contention for a tuple-level lock.  This solves the problem of a
would-be exclusive locker being starved out by an indefinite succession
of share-lockers.  Per recent discussion with Alvaro.

Files

PathChange+/−
src/backend/access/heap/heapam.c modified +206 −88
src/backend/storage/lmgr/lmgr.c modified +125 −1
src/include/storage/lmgr.h modified +18 −1