pgsql/contrib/userlock (user_locks.c)

From: tgl(at)postgresql(dot)org
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql/contrib/userlock (user_locks.c)
Date: 2000-12-22 00:51:53
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-committers

Date: Thursday, December 21, 2000 @ 19:51:53
Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/contrib/userlock

Modified Files:

----------------------------- 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

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.

Browse pgsql-committers by date

  From Date Subject
Next Message tgl 2000-12-22 00:51:54 pgsql/src/backend/storage/ipc (ipci.c)
Previous Message petere 2000-12-21 22:55:27 pgsql/doc/src/sgml (arch-dev.sgml cvs.sgml datetime.sgml history.sgml jdbc.sgml lobj.sgml notation.sgml protocol.sgml release.sgml syntax.sgml xfunc.sgml)