From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: stephan.volz@de.ibm.com
Subject: Wording for using the lock timeout setting
Date: Wed, 03 Apr 2024 11:41:29 +0000
Message-ID: <171214448951.684.1245168459582460039@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/runtime-config-client.html
Description:
Thanks for the cool product. One comment concerning the lock_timeout
parameter:
The documentation states here:
https://www.postgresql.org/docs/16/runtime-config-client.html
"Setting lock_timeout in postgresql.conf is not recommended because it would
affect all sessions."
From my perspective this statement is too strong. There are complex
transaction scenarios where multiple sessions can block the whole system and
a finite value would make sense. When you state "not recommended" this
property is not available in AWS Aurora for example for this reason. I would
assume as you and a number of other database vendors offer such a property,
it should also be usable?
Just a proposal (you might find a better wording):
"Be aware that setting lock_timeout in postgresql.conf would affect all
sessions."
Thanks for consideration.
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-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, stephan.volz@de.ibm.com
Subject: Re: Wording for using the lock timeout setting
In-Reply-To: <171214448951.684.1245168459582460039@wrigleys.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