| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Ajay Pratap <ajaypratap(at)drishti-soft(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL ping/pong to client |
| Date: | 2019-04-17 16:41:57 |
| Message-ID: | CA+bJJbyRp9Y8iQ3zDyJgBZDP4OsP4zA3uJ7=qCBEhC5dYoAWuw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 17, 2019 at 4:49 PM Ajay Pratap <ajaypratap(at)drishti-soft(dot)com> wrote:
> Correction: I meant when my java application dies postgres should break all the connections that were associated with that peer.
And how is the server supposed to detect that without keepalives? TCP
is dessigned to survice for extended period of times without traffic,
I used that a lot in the dial up times.
And what makes you think keepalives are impactful and unrealistic? I
use them a lot, they do not impact my workloads measurably.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-17 17:04:20 | Re: PostgreSQL ping/pong to client |
| Previous Message | Adrian Klaver | 2019-04-17 16:15:25 | Re: Alter domain type / avoiding table rewrite |