Remove support for 'userlocks'? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Remove support for 'userlocks'?
Date
Msg-id 201106031801.p53I1ft12279@momjian.us
Whole thread Raw
Responses Re: Remove support for 'userlocks'?
Re: Remove support for 'userlocks'?
List 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 asfor trace_locks, only for
userlocks.User locks were removed as of PostgreSQL version 8.2. This optioncurrently has no effect.This parameter is
onlyavailable if the LOCK_DEBUG macro was definedwhen PostgreSQL was compiled.
 

Should we remove this parameter and the supporting code since pre-8.2 is
now end-of-life?

-- Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Domains versus polymorphic functions, redux
Next
From: "Kevin Grittner"
Date:
Subject: Re: SIREAD lock versus ACCESS EXCLUSIVE lock