aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2011-11-10 17:54:27 -0500
committerRobert Haas <rhaas@postgresql.org>2011-11-10 17:54:27 -0500
commit71b2b657c034743f81ae7906d7b0fcc8e9a0a6a3 (patch)
tree14c5210e25e8ac151328ae26832f5a254c4f23af /doc/src
parentcf22e851b6ae8737f3e767dffcadf1722fbb36a7 (diff)
downloadpostgresql-71b2b657c034743f81ae7906d7b0fcc8e9a0a6a3.tar.gz
postgresql-71b2b657c034743f81ae7906d7b0fcc8e9a0a6a3.zip
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.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml22
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 3ace7dfa930..18b39ea0a97 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -6218,6 +6218,28 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
</varlistentry>
<varlistentry>
+ <term><varname>trace_userlocks</varname> (<type>boolean</type>)</term>
+ <indexterm>
+ <primary><varname>trace_userlocks</> configuration parameter</primary>
+ </indexterm>
+ <listitem>
+ <para>
+ If on, emit information about user lock usage. Output is the same
+ as for <symbol>trace_locks</symbol>, only for user locks.
+ </para>
+ <para>
+ User locks were removed as of PostgreSQL version 8.2. This option
+ currently has no effect.
+ </para>
+ <para>
+ This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
+ macro was defined when <productname>PostgreSQL</productname> was
+ compiled.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term><varname>trace_lock_oidmin</varname> (<type>integer</type>)</term>
<indexterm>
<primary><varname>trace_lock_oidmin</> configuration parameter</primary>