projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 47458f8) | patch
Use the standard lock manager to establish priority order when there
authorTom Lane <[email protected]>
Sat, 30 Apr 2005 19:03:33 +0000 (19:03 +0000)
committerTom Lane <[email protected]>
Sat, 30 Apr 2005 19:03:33 +0000 (19:03 +0000)
commit93b24772782e7518dee2f85366aa7a80a2beb937
tree395c47bdb56cde5a2bd8d55f4909c8b526c0adc7tree
parent47458f8c2fd97be1637343758223d78fc31f61f8commit | diff
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.
src/backend/access/heap/heapam.c diff | blob | blame | history
src/backend/storage/lmgr/lmgr.c diff | blob | blame | history
src/include/storage/lmgr.h diff | blob | blame | history
This is the main PostgreSQL git repository.