Re: close inactive client connection

Thanks, Scott.

I change the setting and then find out why they were losing the
client connection.
--
Luiz Agnaldo Bernardi
Fone 41 36755756
     41 99979849

On Fri, 25 Sep 2009 11:11:52 -0600
 Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> 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.