Re: Remove support for 'userlocks'?

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: Remove support for 'userlocks'?
Дата
Msg-id BANLkTikABWjf6C47-fOvj0V7e09P7XwTJg@mail.gmail.com
обсуждение исходный текст
Ответ на Remove support for 'userlocks'?  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On Fri, Jun 3, 2011 at 1:01 PM, Bruce Momjian <bruce@momjian.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Merlin Moncure
Дата:
Сообщение: Re: Streaming solution and v3.1 protocol
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Domains versus polymorphic functions, redux