Re: TCP keepalive support for libpq - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: TCP keepalive support for libpq
Date
Msg-id db471ace1002110833v708f7f60xd07e9534cdb3cf20@mail.gmail.com
Whole thread Raw
In response to Re: TCP keepalive support for libpq  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: TCP keepalive support for libpq
Re: TCP keepalive support for libpq
List pgsql-hackers
From the Slony-I docs (http://www.slony.info/documentation/faq.html) :

"Supposing you experience some sort of network outage, the connection
between slon and database may fail, and the slon may figure this out
long before the PostgreSQL  instance it was connected to does. The
result is that there will be some number of idle connections left on
the database server, which won't be closed out until TCP/IP timeouts
complete, which seems to normally take about two hours. For that two
hour period, the slon will try to connect, over and over, and will get
the above fatal message, over and over. "

Speaking as someone who uses Slony quite a lot, this patch sounds very
helpful. Why hasn't libpq had keepalives for years?

Regards,
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Koichi Suzuki
Date:
Subject: Bug on pg_lesslog
Next
From: Andrew Chernow
Date:
Subject: Re: TCP keepalive support for libpq