postgresql/src/backend/storage
Tom Lane 93b2477278 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.
2005-04-30 19:03:33 +00:00
..
buffer Remove unnecessary calls of FlushRelationBuffers: there is no need 2005-03-20 22:00:54 +00:00
file Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
freespace Update VACUUM VERBOSE FSM message, per Tom. 2005-04-24 03:51:49 +00:00
ipc Implement sharable row-level locks, and use them for foreign key references 2005-04-28 21:47:18 +00:00
large_object Completion of project to use fixed OIDs for all system catalogs and 2005-04-14 20:03:27 +00:00
lmgr Use the standard lock manager to establish priority order when there 2005-04-30 19:03:33 +00:00
page Create a routine PageIndexMultiDelete() that replaces a loop around 2005-03-22 06:17:03 +00:00
smgr Remove unnecessary calls of FlushRelationBuffers: there is no need 2005-03-20 22:00:54 +00:00
Makefile $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00