pgsql: Revert removal of trace_userlocks, because userlocks aren't gone - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Revert removal of trace_userlocks, because userlocks aren't gone
Date
Msg-id E1ROdae-0001qF-Jh@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Avoid platform-dependent infinite loop in pg_dump.
Next
From: Robert Haas
Date:
Subject: pgsql: Correct documentation for trace_userlocks.