pgsql: Revert removal of trace_userlocks, because userlocks aren't gone

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Revert removal of trace_userlocks, because userlocks aren't gone
Date: 2011-11-10 22:59:24
Message-ID: E1ROdae-0001qF-Jh@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert removal of trace_userlocks, because userlocks aren't gone.

This reverts commit 0180bd6180511875db046bf8ddcaa633a2952dfd.
contrib/userlock is gone, but user-level locking still exists,
and is exposed via the pg_advisory* family of functions.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/71b2b657c034743f81ae7906d7b0fcc8e9a0a6a3

Modified Files
--------------
doc/src/sgml/config.sgml | 22 ++++++++++++++++++++++
src/backend/storage/lmgr/lock.c | 8 +++++++-
src/backend/utils/misc/check_guc | 2 +-
src/backend/utils/misc/guc.c | 10 ++++++++++
src/include/storage/lock.h | 1 +
5 files changed, 41 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2011-11-10 23:04:13 pgsql: Correct documentation for trace_userlocks.
Previous Message Tom Lane 2011-11-10 21:10:14 pgsql: Avoid platform-dependent infinite loop in pg_dump.