On Thu, Jul 23, 2026 at 10:25 AM Jakub Wartak
<jakub.wartak@enterprisedb.com> wrote:
>
> On Mon, Jul 20, 2026 at 3:16 PM Robert Haas <robertmhaas@gmail.com> wrote:
[..]
After some quick offline follow-up chat with Robert last Thursday, he
helped me to steer more this towards emergency logging in case of overloaded
postmaster rather constant logging of postmaster statistics. One can think
of it something like 'checkpoints happening too fast', but for postmaster.
Now the GUC/concept is called log_excess_connection_attempts, however it is
based on postmaster's CPU time or delay in getting CPU scheduled at all.
I think name is nice, but one can argue it should be
log_excess_postmaster_cpu_time too technically, but I find it way too long.
I've did not wanted to clobber more the logging output, so the HINT line is
not there, but now documentation has tip what to check (and btw it is off by
default, so only people suspecting/debugging something would be getting any
of this)
There's one problem with github CI (and probably buildfarm), not being good
place to test it (apparently ~8 VCPUs are not enough to overload with pgbench
--connect the postamster), so that test is there, but commented out mostly.
-J.
