Re: Remove support for 'userlocks'?

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove support for 'userlocks'?
Date: 2011-06-03 18:22:35
Message-ID: BANLkTikABWjf6C47-fOvj0V7e09P7XwTJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 3, 2011 at 1:01 PM, Bruce Momjian <bruce(at)momjian(dot)us> 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-06-03 18:27:19 Re: Domains versus polymorphic functions, redux
Previous Message Merlin Moncure 2011-06-03 18:19:04 Re: Streaming solution and v3.1 protocol