From: | "Didier Gasser-Morlay" <didiergm(at)gmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Client connection lost; still in the task list |
Date: | 2008-04-24 09:12:47 |
Message-ID: | 608b66ce0804240212t2c691987wcdee24754a289066@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Resucing the tcp_keepalive to 900 seconds did help immensely
thanks for the advice Tom
Didier
>You're right, this morning most connections had been freed.
>
>I have seen that the tcp_keepalive
> is 7200 second, I'll shorten that to see.
>thanks
>Didier
On Tue, Apr 22, 2008 at 7:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Didier Gasser-Morlay" <didiergm(at)gmail(dot)com> writes:
> > So my question is what makes PostgreSQL realise that a connection is
> > dead ? when will it drop it and free the connection ?
>
> It'll drop it when the kernel tells it the connection is dead.
> Standard TCP timeouts are measured in hours, though. You might
> be able to get a shorter timeout to be applied by fooling with
> the "keepalive" parameters, if those can be adjusted on your platform.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Didier Gasser-Morlay | 2008-04-24 09:18:19 | Limiting the number of connections for one user |
Previous Message | Didier Gasser-Morlay | 2008-04-24 09:08:12 | Changing a trigger function |