Re: tcp keep alive don't work when the backend is busy - Mailing list pgsql-general

From Tom Lane
Subject Re: tcp keep alive don't work when the backend is busy
Date
Msg-id 4781.1575990387@sss.pgh.pa.us
Whole thread Raw
In response to tcp keep alive don't work when the backend is busy  (Олег Самойлов <splarv@ya.ru>)
Responses Re: tcp keep alive don't work when the backend is busy
List pgsql-general
=?utf-8?B?0J7Qu9C10LMg0KHQsNC80L7QudC70L7Qsg==?= <splarv@ya.ru> writes:
> According to the documentation
> https://www.postgresql.org/docs/12/runtime-config-connection.html
> A backend must check connection to the client by tcp_keepalive messages. (Config option tcp_keepalives_idle).

> But this is don't work if the backend is busy.

You're reading something into the documentation that isn't there.

The TCP keepalive mechanism is something that the OS does, independently
of backend processing.  The backend isn't going to notice loss of client
connection until it tries to read or write on the connection.

If it were free to improve this, we might do so.  But it would be
very much not free.

            regards, tom lane



pgsql-general by date:

Previous
From: stan
Date:
Subject: Re: server will not start (Debian)
Next
From: Fabio Ugo Venchiarutti
Date:
Subject: Re: tcp keep alive don't work when the backend is busy