| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Marat Buharov <marat(dot)buharov(at)gmail(dot)com> |
| Subject: | Re: client_connection_check_interval default value |
| Date: | 2026-02-05 17:26:34 |
| Message-ID: | CAOYmi+nS69LiUExZF=gGZ+NJU-SCNQ59qJTiWtJw96cDdi9iSg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 4, 2026 at 9:30 PM Jeremy Schneider
<schneider(at)ardentperf(dot)com> wrote:
> While a fix has been merged in pgx for the most direct root cause of
> the incident I saw, this setting just seems like a good behavior to
> make Postgres more robust in general.
At the risk of making perfect the enemy of better, the protocol-level
heartbeat mentioned in the original thread [1] would cover more use
cases, which might give it a better chance of eventually becoming
default behavior. It might also be a lot of work, though.
--Jacob
[1] https://postgr.es/m/CA%2BhUKGLyj5Aqt6ojYfSc%2BqSeB1x%3D3RbU61hnus5sL0BKqEBsLw%40mail.gmail.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavlo Golub | 2026-02-05 17:35:27 | Re: Re[2]: [PATCH] Add last_executed timestamp to pg_stat_statements |
| Previous Message | Andres Freund | 2026-02-05 17:21:22 | Re: Fix pg_stat_get_backend_wait_event() for aux processes |