Thank you all for your feedback. I've checked both server and client side and :
a) libpq by default enables keepalive b) in postgresql.conf tcp_keepalives_idle=0 (default setting) means - apply system default Is there any chance that it's NOT fired on RHEL7 acting as SQL server for some reasons? I'll be able to check this next morning. Regards Marcin Od: "Tom Lane" <t...@sss.pgh.pa.us> Do: "Francisco Olarte" <fola...@peoplecall.com> DW: "depesz" <dep...@depesz.com>, "Marcin Giedz" <marcin.gi...@arise.pl>, pgsql-general@postgresql.org Wysłane: czwartek, 27 październik 2016 18:32:54 Temat: Re: [GENERAL] libpq heartbeat Francisco Olarte <fola...@peoplecall.com> writes: > On Thu, Oct 27, 2016 at 5:01 PM, hubert depesz lubaczewski > <dep...@depesz.com> wrote: >> On Thu, Oct 27, 2016 at 04:43:55PM +0200, Marcin Giedz wrote: >>> I'm wondering if there is any natural implementation of heartbeats in >>> libpq library? >> check tcp_keepalives_* in postgresql.conf > Isn't this a server setting, and so going to affect every connection, Yes, but there are equivalent libpq parameters for firing heartbeat pings from the client side. Those are per-connection. https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS regards, tom lane
