public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Alfonso Escribano <[email protected]>
Cc: [email protected]
Subject: Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters
Date: Wed, 03 Dec 2025 12:36:30 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Alfonso Escribano <[email protected]> writes:
>     When client_connection_check_interval has any value, and
>     log_lock_waits is enabled, the postgresql log displays a message
>     about lock waits with the frequency of
>     client_connection_check_interval.

When log_lock_waits is enabled, we'll print that "still waiting"
message anytime ProcSleep is awoken from a wait-for-lock sleep,
if it's already waited deadlock_timeout or longer.  Normally there
isn't much that would awaken such a process other than being granted
the lock.  But here, you've set client_connection_check_interval
so short that that interrupt happens repeatedly while waiting.

Why in the world would you want client_connection_check_interval
as short as 10 ms?  Sane values would probably be more like 10 s.

			regards, tom lane

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox