pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17048: about trace_locks parameter problem
2+ messages / 2 participants
[nested] [flat]
* BUG #17048: about trace_locks parameter problem
@ 2021-06-04 22:46 PG Bug reporting form <noreply@postgresql.org>
2021-06-05 00:21 ` Re: BUG #17048: about trace_locks parameter problem Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2021-06-04 22:46 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: leiyanliang@highgo.com
The following bug has been logged on the website:
Bug reference: 17048
Logged by: yanliang lei
Email address: leiyanliang@highgo.com
PostgreSQL version: 13.3
Operating system: CentOS7.6
Description:
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
this problem also applies to PostgreSQL 14 Beta1 Version。
postgres=# select name from pg_settings where name like '%lock%';
name
--------------------------------
block_size
deadlock_timeout
lock_timeout
log_lock_waits
max_locks_per_transaction
max_pred_locks_per_page
max_pred_locks_per_relation
max_pred_locks_per_transaction
wal_block_size
(9 rows)
postgres=# select name from pg_settings where name='trace_locks';
---->>>there is no trace_locks parameter
name
------
(0 rows)
postgres=# select version();
version
---------------------------------------------------------------------------------------------------------
PostgreSQL 13.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5
20150623 (Red Hat 4.8.5-44), 64-bit
(1 row)
postgres=#
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #17048: about trace_locks parameter problem
2021-06-04 22:46 BUG #17048: about trace_locks parameter problem PG Bug reporting form <noreply@postgresql.org>
@ 2021-06-05 00:21 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2021-06-05 00:21 UTC (permalink / raw)
To: leiyanliang@highgo.com; +Cc: pgsql-bugs@lists.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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2021-06-05 00:21 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-06-04 22:46 BUG #17048: about trace_locks parameter problem PG Bug reporting form <noreply@postgresql.org>
2021-06-05 00:21 ` Tom Lane <tgl@sss.pgh.pa.us>
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