pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: leiyanliang@highgo.com
Subject: BUG #17048: about trace_locks parameter problem
Date: Fri, 04 Jun 2021 22:46:48 +0000
Message-ID: <17048-771af7a9c54fea93@postgresql.org> (raw)

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=#



view thread (2+ messages)  latest in thread

Message-ID: <17048-771af7a9c54fea93@postgresql.org>
Permalink:  ../17048-771af7a9c54fea93@postgresql.org/
Also on:    postgresql.org/message-id/17048-771af7a9c54fea93@postgresql.org

 · 

reply

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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, leiyanliang@highgo.com
  Subject: Re: BUG #17048: about trace_locks parameter problem
  In-Reply-To: <17048-771af7a9c54fea93@postgresql.org>

* 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