Thanks for your answer. I was afraid someone would say that...
I was hoping that the keepalives would be more of a matter of cooperation between postgres and the OS.
On Wed, Dec 14, 2022 at 10:52 AM Laurenz Albe <laurenz.albe@xxxxxxxxxxx> wrote:
On Wed, 2022-12-14 at 08:55 +0100, Willy-Bas Loos wrote:
> Some users of our database have a NAT firewall and keep a postgres client (e.g. pgAdmin )
> open for hours. To prevent the connection from being killed by the firewall due to inactivity,
> we configured tcp_keepalives_idle = 120 so that the server sends keepalives and keeps the
> connection active. (this is on debian)
>
> We've recently upgraded from postgres 9.3 to 13 and from debian 6 to 11.
> I'm getting the complaint that since the upgrade, the connection breaks. But only when they run a long query.
>
> Has anything changed in postgres that might cause this? e.g. that keepalives are only sent when the session is idle?
It is the operating system kernel that sends keepalives, so that should be independent of
what the PostgreSQL backend is doing.
Yours,
Laurenz Albe
--
Willy-Bas Loos
