Re: BUG #17048: about trace_locks parameter problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: leiyanliang(at)highgo(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17048: about trace_locks parameter problem
Date: 2021-06-05 00:21:22
Message-ID: 507253.1622852482@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> in the following SQL statement's result ,there is no trace_locks
> parameter.
> but in the
> documents(https://www.postgresql.org/docs/current/runtime-config-developer.html),there
> is trace_locks parameter

Note where that page says

This parameter is only available if the LOCK_DEBUG macro was defined
when PostgreSQL was compiled.

Most builds don't have that turned on.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dilip Kumar 2021-06-05 04:44:42 Re: logical decoding bug: segfault in ReorderBufferToastReplace()
Previous Message Alvaro Herrera 2021-06-05 00:07:05 Re: logical decoding bug: segfault in ReorderBufferToastReplace()