pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guido Barosio <gbarosio@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Blocking connection and timeout problem
Date: Wed, 3 Aug 2005 16:08:21 +0100
Message-ID: <f7f6b4c70508030808be9c192@mail.gmail.com> (raw)
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB16822@neptun.sonorys.at>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB16822@neptun.sonorys.at>

Used to have this problem also with pgadmin connections, that didn't close
some sessions remain there, for a period, and you must kill them to continue 

without a restart of the service. 

scenery:
pgsql >= 7.4.3 , not tested on >=8
pgadmin <= 1.0.2


On other layer of this issue, this should be also related with some in deep 
tcp/ip settings.
ie, I know that in order to keep an <idle> ssh session open for a longer 
time, you shall touch some values somewhere *not* in the main ssh_config 
file. (a global parameter for the OS) And this will keep your session open 
for a longer time. 

If this is particular for every OS, that could explain a longer time on your 
case, and 1 or 2 hours in Tom's case.

Anyway, I would like to hear a little bit about this, cause it's a little 
bit difficult to find such cases, 
we always end on the problem lacking, without a previous warn. (and that is 
bad, for a DBA at least).

Regards,
Guido



On 8/3/05, KÖPFERL Robert <robert.koepferl@sonorys.at> 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?= <robert.koepferl@sonorys.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
> 



-- 
"Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.

view thread (8+ messages)  latest in thread

Message-ID: <f7f6b4c70508030808be9c192@mail.gmail.com>
Permalink:  ../f7f6b4c70508030808be9c192@mail.gmail.com/
Also on:    postgresql.org/message-id/f7f6b4c70508030808be9c192@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: gbarosio@gmail.com
  Subject: Re: Blocking connection and timeout problem
  In-Reply-To: <f7f6b4c70508030808be9c192@mail.gmail.com>
  References: <ED4E30DD9C43D5118DFB00508BBBA76EB16822@neptun.sonorys.at> <f7f6b4c70508030808be9c192@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox