Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1lpK4A-0000XF-4x
	for pgsql-bugs@arkaria.postgresql.org; Sat, 05 Jun 2021 00:21:30 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1lpK48-0008Vi-9o
	for pgsql-bugs@arkaria.postgresql.org; Sat, 05 Jun 2021 00:21:28 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1lpK48-0008VL-3S
	for pgsql-bugs@lists.postgresql.org; Sat, 05 Jun 2021 00:21:28 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1lpK45-0003gO-S4
	for pgsql-bugs@lists.postgresql.org; Sat, 05 Jun 2021 00:21:27 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 1550LMdA507254;
	Fri, 4 Jun 2021 20:21:23 -0400
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
In-reply-to: <17048-771af7a9c54fea93@postgresql.org>
References: <17048-771af7a9c54fea93@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 04 Jun 2021 22:46:48 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <507252.1622852482.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 04 Jun 2021 20:21:22 -0400
Message-ID: <507253.1622852482@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/507253.1622852482%40sss.pgh.pa.us>
Precedence: bulk

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-develop=
er.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