From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
---|---|
To: | Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: libpq heartbeat |
Date: | 2016-10-27 15:01:09 |
Message-ID: | CA+bJJbyGhyJzb619C5Htg12hCcs8igj7SeyoMo9hjDVuOCOGHA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Marcin:
On Thu, Oct 27, 2016 at 4:43 PM, Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl> wrote:
> I'm wondering if there is any natural implementation of heartbeats in libpq
> library? We've been facing specially in firewall env occasionally session
> drops between client and server. Extending session timeout directly on
> firewalls is not possible (company rules). Perhaps there is such mechanism
> "somewhere" to avoid reimplementation ?
RTFM? Now, seriously. Have you read
https://www.postgresql.org/docs/9.6/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS,
specifically search for keepalive. Keepalives generate traffic which
normally keeps overzealous firewalls happy, I have used it before
successfully.
And I'd like to point libpq sessions does not sound to be the best
kind of traffic across a firewall, not a good service / protocol to
expose.
Francisco Olarte.
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2016-10-27 15:03:43 | Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1 |
Previous Message | hubert depesz lubaczewski | 2016-10-27 15:01:05 | Re: libpq heartbeat |