Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Client connection lost; still in the task list
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Didier Gasser-Morlay" <didiergm(at)gmail(dot)com>
- Cc: pgsql-novice(at)postgresql(dot)org
- Subject: Re: Client connection lost; still in the task list
- Date: Tue, 22 Apr 2008 13:29:28 -0400
- Message-id: <24431.1208885368@sss.pgh.pa.us> <text/plain>
"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
- Follow-Ups:
- Re: Client connection lost; still in the task list
- From: Didier Gasser-Morlay
- Re: Client connection lost; still in the task list
- References:
- Client connection lost; still in the task list
- From: Didier Gasser-Morlay
- Client connection lost; still in the task list
- Prev by Date: Client connection lost; still in the task list
- Next by Date: pgoptions syntax?
- Previous by thread: Client connection lost; still in the task list
- Next by thread: Re: Client connection lost; still in the task list
- Indexes: