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

From Merlin Moncure
Subject Re: Remove support for 'userlocks'?
Date
Msg-id [email protected]
Whole thread Raw
In response to Remove support for 'userlocks'?  (Bruce Momjian <[email protected]>)
List pgsql-hackers
On Fri, Jun 3, 2011 at 1:01 PM, Bruce Momjian <[email protected]> wrote:
> 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?

hm, shouldn't it be replaced with trace_advisory_locks?

merlin


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Streaming solution and v3.1 protocol
Next
From: Tom Lane
Date:
Subject: Re: Domains versus polymorphic functions, redux