From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Luiz Bernardi <lb(at)cplinformatica(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: close inactive client connection |
Date: | 2009-09-25 17:11:52 |
Message-ID: | dcc563d10909251011k7e168fa8yeff16c87d0fb94c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Sep 25, 2009 at 6:26 AM, Luiz Bernardi <lb(at)cplinformatica(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-09-25 17:31:03 | Re: generic modelling of data models; enforcing constraints dynamically... |
Previous Message | John R Pierce | 2009-09-25 17:03:20 | Re: close inactive client connection |