Re: close inactive client connection - Mailing list pgsql-general

From Scott Marlowe
Subject Re: close inactive client connection
Date
Msg-id dcc563d10909251011k7e168fa8yeff16c87d0fb94c@mail.gmail.com
Whole thread Raw
In response to close inactive client connection  ("Luiz Bernardi" <lb@cplinformatica.com>)
Responses Re: close inactive client connection  ("Luiz Bernardi" <lb@cplinformatica.com>)
List pgsql-general
On Fri, Sep 25, 2009 at 6:26 AM, Luiz Bernardi <lb@cplinformatica.com> wrote:
> Hello,
>
> I am developing a system, using the ZeosLib, which maintains a permanent
> connection to the database.
>
> When the client loses the connection, the server does not recognize this and
> keeps the connection as if it were active. When the client attempts to
> reconnect, the server creates a new connection and the previous remains
> active.

Eventually the server's network stack will check to see if the
connection is alive or not by sending a tcp keepalive ping.  If it
receives no answers after x number of tries, it will close the socket
and the pg backend will be terminated.

To adjust this time, look at the tcp keepalive parameters in either
the postgresql.conf file or system wide on your server.  The default
timeout is 2 hours.  It's not unusual to drop it to 5 or 10 minutes on
busy systems.

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: close inactive client connection
Next
From: Sam Mason
Date:
Subject: Re: generic modelling of data models; enforcing constraints dynamically...