From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Remove support for 'userlocks'? |
Date: | 2011-06-03 18:01:41 |
Message-ID: | 201106031801.p53I1ft12279@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
According to our documentation, 'userlocks' were removed in PG 8.2:
http://developer.postgresql.org/pgdocs/postgres/runtime-config-developer.html
trace_userlocks (boolean)
If on, emit information about user lock usage. Output is the same as
for trace_locks, only for user locks.
User locks were removed as of PostgreSQL version 8.2. This option
currently has no effect.
This parameter is only available if the LOCK_DEBUG macro was defined
when PostgreSQL was compiled.
Should we remove this parameter and the supporting code since pre-8.2 is
now end-of-life?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-06-03 18:04:19 | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
Previous Message | Noah Misch | 2011-06-03 17:53:23 | Re: Domains versus polymorphic functions, redux |