X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 098B09DC806
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Mon,  9 Jan 2006 11:48:19 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 90315-10
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Mon,  9 Jan 2006 11:48:23 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from mail.skype.net (mail.skype.net [195.215.8.149])
	by postgresql.org (Postfix) with ESMTP id A208A9DC809
	for <pgsql-hackers@postgresql.org>;
	Mon,  9 Jan 2006 11:48:16 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.skype.net (Postfix) with ESMTP id 52E8E4DD95;
	Mon,  9 Jan 2006 16:48:20 +0100 (CET)
Received: from [192.168.0.95] (joltid-gw.joltid.org [195.50.194.24])
	by mail.skype.net (Postfix) with ESMTP id 39AF34DD93;
	Mon,  9 Jan 2006 16:48:17 +0100 (CET)
Subject: Re: Stats collector performance improvement
From: Hannu Krosing <hannu@skype.net>
To: Greg Stark <gsstark@mit.edu>
Cc: Simon Riggs <simon@2ndquadrant.com>,
	Tom Lane <tgl@sss.pgh.pa.us>, Qingqing Zhou <zhouqq@cs.toronto.edu>,
	pgsql-hackers@postgresql.org
In-Reply-To: <87wtha1x87.fsf@stark.xeocode.com>
References: <200601021840.k02Ieed21704@candle.pha.pa.us>
	<11924.1136233224@sss.pgh.pa.us> <dpc4cg$lm6$1@news.hub.org>
	<12503.1136238525@sss.pgh.pa.us>
	<1136281253.5052.113.camel@localhost.localdomain>
	<1136324574.4256.17.camel@localhost.localdomain>
	<87wtha1x87.fsf@stark.xeocode.com>
Content-Type: text/plain; charset=utf-8
Date: Mon, 09 Jan 2006 17:48:21 +0200
Message-Id: <1136821701.4076.1.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.024 required=5 tests=[AWL=0.024]
X-Spam-Score: 0.024
X-Spam-Level: 
X-Archive-Number: 200601/289
X-Sequence-Number: 78393

Ühel kenal päeval, P, 2006-01-08 kell 11:49, kirjutas Greg Stark:
> Hannu Krosing <hannu@skype.net> writes:
> 
> > Interestingly I use pg_stat_activity view to watch for stuck backends,
> > "stuck" in the sense that they have not noticed when client want away
> > and are now waitin the TCP timeout to happen. I query for backends which
> > have been in "<IDLE>" state for longer than XX seconds. I guess that at
> > least some kind of indication for this should be available.
> 
> You mean like the tcp_keepalives_idle option?
> 
> http://www.postgresql.org/docs/8.1/interactive/runtime-config-connection.html#GUC-TCP-KEEPALIVES-IDLE
> 

Kind of, only I'd like to be able to set timeouts less than 120 minutes.

from:
http://developer.apple.com/documentation/mac/NetworkingOT/NetworkingWOT-390.html#HEADING390-0

kp_timeout
        Set the requested timeout value, in minutes. Specify a value of
        T_UNSPEC to use the default value. You may specify any positive
        value for this field of 120 minutes or greater. The timeout
        value is not an absolute requirement; if you specify a value
        less than 120 minutes, TCP will renegotiate a timeout of 120
        minutes.
        
-----------
Hannu