Dmitry Samonenko <shreddingwork@xxxxxxxxx> writes: > On Tue, May 27, 2014 at 2:35 PM, Albe Laurenz <laurenz.albe@xxxxxxxxxx>wrote: >> In PostgreSQL you can handle the problem of dying connections by setting >> the >> tcp_keepalives_* parameters (see >> http://www.postgresql.org/docs/current/static/runtime-config-connection.html >> ). >> >> That should take care of the problem, right? > I am afraid it won't help: > 1. AFAIK, in Linux TCP keepalive is used on idle connections only. If not > all data is transmitted - connection is not idle - keep alive timer is not > started. > 2. POLLHUP mask is used (while setting poll fds) to catch keep alive > timeout. Sadly, libpq sets (POLLIN | POLLERR). Would you provide some evidence for these claims? If the keepalive stuff didn't work, somebody would certainly have noticed by now. Our general approach to network-error handling is that dropping a connection is a last resort, and thus it's usually inappropriate to try to force the network stack to fail more quickly than it was designed to do. While you can override the keepalive timing if you insist, we won't consider a patch that would make PG use something other than the network stack's default settings by default, if you get my drift. regards, tom lane
