Improve LockAcquire API per my recent proposal. All error conditions
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 29 May 2005 22:45:02 +0000 (22:45 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 29 May 2005 22:45:02 +0000 (22:45 +0000)
commit821d2da8b35a5d5b86480f0fd210f945597ac39b
tree7e50ccf3ab1d330278eaadfaec9bab94186d5334
parentdfb24fb7f99552eecd23918490de549bad8fed03
Improve LockAcquire API per my recent proposal.  All error conditions
are now reported via elog, eliminating the need to test the result code
at most call sites.  Make it possible for the caller to distinguish a
freshly acquired lock from one already held in the current transaction.
Use that capability to avoid redundant AcceptInvalidationMessages() calls
in LockRelation().
contrib/userlock/user_locks.c
src/backend/storage/lmgr/lmgr.c
src/backend/storage/lmgr/lock.c
src/include/storage/lock.h