Re: Blocking connection and timeout problem

From: Dario Brignardello <dbrignar(at)sinectis(dot)com>
To: KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Blocking connection and timeout problem
Date: 2005-08-03 18:50:38
Message-ID: 1123095038.15646.41.camel@aleph.hq.sinectis.com.ar
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(at)sss(dot)pgh(dot)pa(dot)us]
> |Sent: Mittwoch, 03. August 2005 16:38
> |To: KÖPFERL Robert
> |Cc: pgsql-admin(at)postgresql(dot)org
> |Subject: Re: [ADMIN] Blocking connection and timeout problem
> |
> |
> |=?iso-8859-1?Q?K=D6PFERL_Robert?= <robert(dot)koepferl(at)sonorys(dot)at> 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
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2005-08-03 19:39:00 Re: Defer Committing Updates on High-Activity Table
Previous Message Lane Van Ingen 2005-08-03 18:47:14 Defer Committing Updates on High-Activity Table