Re: PostgreSQL ping/pong to client - Mailing list pgsql-general

From Tom Lane
Subject Re: PostgreSQL ping/pong to client
Date
Msg-id 4113.1555520660@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL ping/pong to client  (Francisco Olarte <folarte@peoplecall.com>)
List pgsql-general
Francisco Olarte <folarte@peoplecall.com> writes:
> On Wed, Apr 17, 2019 at 4:49 PM Ajay Pratap <ajaypratap@drishti-soft.com> wrote:
>> Correction: I meant when my java application dies postgres should break all the connections that were associated
withthat 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.

If we tried to do something about that in the server code proper,
we'd basically be reinventing TCP keepalives --- probably badly.
And we couldn't do it at all without a protocol version break,
because the client-side code would also need to know about it.

Just use the keepalive facility.

            regards, tom lane



pgsql-general by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: PostgreSQL ping/pong to client
Next
From: Bruce Momjian
Date:
Subject: Re: Move vs. copy table between databases that share a tablespace?