Re: libpq heartbeat

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:41:54
Message-ID: CA+bJJbyhqoVnvikbjjCi+xtsMti+YqxzEjTko0QQb1m1bvkwwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom:

On Thu, Oct 27, 2016 at 6:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Francisco Olarte <folarte(at)peoplecall(dot)com> writes:
>> Isn't this a server setting, and so going to affect every connection,
> Yes,

Ok, just checking.

> 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

That's what I told the OP ( with nearly the same link ).

Thanks.

Francisco Olarte.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2016-10-27 17:29:17 Re: libpq heartbeat
Previous Message Kim Rose Carlsen 2016-10-27 16:34:58 How to hint two columns IS NOT DISTINCT FROM each other in a join