From: Tom Lane <tgl@sss.pgh.pa.us>
To: leiyanliang@highgo.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17048: about trace_locks parameter problem
Date: Fri, 04 Jun 2021 20:21:22 -0400
Message-ID: <507253.1622852482@sss.pgh.pa.us> (raw)
In-Reply-To: <17048-771af7a9c54fea93@postgresql.org>
References: <17048-771af7a9c54fea93@postgresql.org>
PG Bug reporting form <noreply@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, leiyanliang@highgo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17048: about trace_locks parameter problem
In-Reply-To: <507253.1622852482@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox