| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
| Cc: | hubert depesz lubaczewski <depesz(at)depesz(dot)com>, Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: libpq heartbeat |
| Date: | 2016-10-27 16:32:54 |
| Message-ID: | 3654.1477585974@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Francisco Olarte <folarte(at)peoplecall(dot)com> writes:
> On Thu, Oct 27, 2016 at 5:01 PM, hubert depesz lubaczewski
> <depesz(at)depesz(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kim Rose Carlsen | 2016-10-27 16:34:58 | How to hint two columns IS NOT DISTINCT FROM each other in a join |
| Previous Message | Francisco Olarte | 2016-10-27 16:18:19 | Re: libpq heartbeat |