Re: client_connection_check_interval default value

Greg Sabino Mullane <htamfids@gmail.com>

From: Greg Sabino Mullane <htamfids@gmail.com>

To: Jeremy Schneider <schneider@ardentperf.com>

Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, Marat Buharov <marat.buharov@gmail.com>

Date: 2026-02-05T15:00:29Z

Lists: pgsql-hackers

I'm a weak -1 on this. Certainly not 2s! That's a lot of context switching
for a busy system for no real reason. Also see this past discussion:

https://www.postgresql.org/message-id/CTEB8LNLOHKR.3I6NK8QVBAGSQ@gonk

--
Cheers,
Greg

Commits

Add TAP tests for log_lock_waits
- ca2b5443e2dc 19 (unreleased) landed
Add tests for lock statistics, take two
- 557a9f1e3e62 19 (unreleased) cited
Ensure "still waiting on lock" message is logged only once per wait.
- fd6ecbfa75ff 19 (unreleased) landed