| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Jeff Lanzarotta <delux256-postgresql(at)yahoo(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL GENERAL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How does server handle clients that disconnect ungracefully? |
| Date: | 2007-04-24 16:42:58 |
| Message-ID: | 5004.1177432978@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> The only time the server will wait for a time out is if the server and
> the client are on different machines and something disrupts actual
> communications.
Right, you need connectivity loss to create an issue --- a client
program crash doesn't cause this type of problem. The most common
form of the problem that I've heard about is routers deciding to drop a
connection that's been idle too long.
BTW, on some platforms it's possible to change the timeout settings so
that a lost connection is abandoned more quickly by the TCP stack.
See the tcp_keepalives_xxx parameters if you need to do that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcelo de Moraes Serpa | 2007-04-24 17:00:34 | Re: Audit-trail engine: getting the application's layer user_id |
| Previous Message | Stephan Szabo | 2007-04-24 16:41:26 | Re: hi |