pgsql/contrib/userlock (user_locks.c) - Mailing list pgsql-committers

From tgl@postgresql.org
Subject pgsql/contrib/userlock (user_locks.c)
Date
Msg-id 200012220051.eBM0prI58119@hub.org
Whole thread Raw
List pgsql-committers
  Date: Thursday, December 21, 2000 @ 19:51:53
Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/contrib/userlock
     from hub.org:/home/projects/pgsql/tmp/cvs-serv58115/contrib/userlock

Modified Files:
    user_locks.c

-----------------------------  Log Message  -----------------------------

Revise lock manager to support "session level" locks as well as "transaction
level" locks.  A session lock is not released at transaction commit (but it
is released on transaction abort, to ensure recovery after an elog(ERROR)).
In VACUUM, use a session lock to protect the master table while vacuuming a
TOAST table, so that the TOAST table can be done in an independent
transaction.

I also took this opportunity to do some cleanup and renaming in the lock
code.  The previously noted bug in ProcLockWakeup, that it couldn't wake up
any waiters beyond the first non-wakeable waiter, is now fixed.  Also found
a previously unknown bug of the same kind (failure to scan all members of
a lock queue in some cases) in DeadLockCheck.  This might have led to failure
to detect a deadlock condition, resulting in indefinite waits, but it's
difficult to characterize the conditions required to trigger a failure.


pgsql-committers by date:

Previous
From: tgl@postgresql.org
Date:
Subject: pgsql/src/backend/storage/ipc (ipci.c)
Next
From: Bruce Momjian
Date:
Subject: Re: pgsql/src/backend/access/transam (xact.c)