X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0AB2C5298E for ; Wed, 3 Aug 2005 15:52:54 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 58912-09 for ; Wed, 3 Aug 2005 18:52:45 +0000 (GMT) Received: from amiel.capfed2.sinectis.com.ar (amiel.capfed2.sinectis.com.ar [216.244.211.2]) by svr1.postgresql.org (Postfix) with ESMTP id 01ED152972 for ; Wed, 3 Aug 2005 15:52:43 -0300 (ADT) Received: from aleph.hq.sinectis.com.ar (patix.sinectis.com.ar [216.244.192.23]) by amiel.capfed2.sinectis.com.ar (Postfix) with ESMTP id 5164F3255B; Wed, 3 Aug 2005 15:52:43 -0300 (ART) Subject: Re: Blocking connection and timeout problem From: Dario Brignardello Reply-To: dbrignar@uolsinectis.com.ar To: =?ISO-8859-1?Q?K=D6PFERL?= Robert Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-2 Organization: UOL Argentina. Date: Wed, 03 Aug 2005 15:50:38 -0300 Message-Id: <1123095038.15646.41.camel@aleph.hq.sinectis.com.ar> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200508/42 X-Sequence-Number: 18361 Assuming you are on a linux box (Not sure if it's stated in your mail, sorry if I missed that) you could set /proc/sys/net/ipv4/tcp_keepalive_time to a lower value. That should do the trick. Hope this helps Greetings Dario On Wed, 2005-08-03 at 16:48 +0200, KÖPFERL Robert wrote: > > > > |-----Original Message----- > |From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > |Sent: Mittwoch, 03. August 2005 16:38 > |To: KÖPFERL Robert > |Cc: pgsql-admin@postgresql.org > |Subject: Re: [ADMIN] Blocking connection and timeout problem > | > | > |=?iso-8859-1?Q?K=D6PFERL_Robert?= writes: > |> Why is that? Why isn't client A's transaction detected as dead ? > | > |It will be eventually, when the TCP connection times out. The standard > |timeout is generally an hour or two :-( > > Seems not like so. I waited for two hours and it still existed. > > But non-the-less. Can this timeout be configured to be less? > > | > | regards, tom lane > | > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend >