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 7685752A34 for ; Wed, 3 Aug 2005 12:08:26 -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 84118-10 for ; Wed, 3 Aug 2005 15:08:24 +0000 (GMT) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.195]) by svr1.postgresql.org (Postfix) with ESMTP id 86EE5529F2 for ; Wed, 3 Aug 2005 12:08:22 -0300 (ADT) Received: by nproxy.gmail.com with SMTP id c2so37471nfe for ; Wed, 03 Aug 2005 08:08:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:references; b=s95/6EwkDcOa8OXSPM1qq3C+KvxAtMueob1nrwDSDK/7Glx+sDey9dh/4EsXJIZLPQs2wrUAl946egio7QCq6JrGL/u832IVoTVxJiMs+xGLL+p26hDjnkVZaEE7GKnsswqtTFU093It8Yz9pzCZId0mepOPs0cAUubhlOIoYlU= Received: by 10.48.250.16 with SMTP id x16mr27467nfh; Wed, 03 Aug 2005 08:08:21 -0700 (PDT) Received: by 10.48.144.16 with HTTP; Wed, 3 Aug 2005 08:08:21 -0700 (PDT) Message-ID: Date: Wed, 3 Aug 2005 16:08:21 +0100 From: Guido Barosio Subject: Re: Blocking connection and timeout problem Cc: pgsql-admin@postgresql.org In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1965_14407593.1123081701492" References: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.388 tagged_above=0 required=5 tests=AWL, HTML_20_30, HTML_MESSAGE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200508/34 X-Sequence-Number: 18353 ------=_Part_1965_14407593.1123081701492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 continu= e=20 without a restart of the service.=20 scenery: pgsql >=3D 7.4.3 , not tested on >=3D8 pgadmin <=3D 1.0.2 On other layer of this issue, this should be also related with some in deep= =20 tcp/ip settings. ie, I know that in order to keep an ssh session open for a longer=20 time, you shall touch some values somewhere *not* in the main ssh_config=20 file. (a global parameter for the OS) And this will keep your session open= =20 for a longer time.=20 If this is particular for every OS, that could explain a longer time on you= r=20 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= =20 bit difficult to find such cases,=20 we always end on the problem lacking, without a previous warn. (and that is= =20 bad, for a DBA at least). Regards, Guido On 8/3/05, K=D6PFERL Robert wrote: >=20 >=20 >=20 > |-----Original Message----- > |From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > |Sent: Mittwoch, 03. August 2005 16:38 > |To: K=D6PFERL Robert > |Cc: pgsql-admin@postgresql.org > |Subject: Re: [ADMIN] Blocking connection and timeout problem > | > | > |=3D?iso-8859-1?Q?K=3DD6PFERL_Robert?=3D wri= tes: > |> 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 :-( >=20 > Seems not like so. I waited for two hours and it still existed. >=20 > But non-the-less. Can this timeout be configured to be less? >=20 > | > | regards, tom lane > | >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend >=20 --=20 "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. ------=_Part_1965_14407593.1123081701492 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Used to have this problem also with pgadmin connections, that didn't close<= br> some sessions remain there, for a period, and you must kill them to continu= e
without a restart of the service.

scenery:
pgsql >=3D 7.4.3 , not tested on >=3D8
pgadmin  <=3D 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 you= r 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 b= it 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=D6PFERL Robert <robert.koepferl@sonorys.at> wrote:


|-----Original Message-----
|From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
|Sent: Mittwoch, 03. Aug= ust 2005 16:38
|To: K=D6PFERL Robert
|Cc: pgsql-admin@postgresql.org
|Subject: Re: [ADMIN] Blocking connection= and timeout problem
|
|
|=3D?iso-8859-1?Q?K=3DD6PFERL_Robert?=3D = <robert.koepferl@sonorys.a= t > writes:
|> Why is that? Why isn't client A's transaction detecte= d as dead ?
|
|It will be eventually, when the TCP connection times o= ut.  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?
|
|           &n= bsp;           regards, tom lane
|

---------------------------(end of broadcast)= ---------------------------
TIP 6: explain analyze is your friend



--
"Adopting the positio= n that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
perfo= rmance, not more" - Tom Lane. ------=_Part_1965_14407593.1123081701492--