Re: tcp keep alive don't work when the backend is busy
| От | Tom Lane |
|---|---|
| Тема | Re: tcp keep alive don't work when the backend is busy |
| Дата | |
| Msg-id | 4781.1575990387@sss.pgh.pa.us обсуждение |
| Ответ на | tcp keep alive don't work when the backend is busy (Олег Самойлов <splarv@ya.ru>) |
| Ответы |
Re: tcp keep alive don't work when the backend is busy
|
| Список | 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 по дате отправления: