pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Hannu Krosing <hannu@skype.net>
To: Greg Stark <gsstark@mit.edu>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Qingqing Zhou <zhouqq@cs.toronto.edu>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Stats collector performance improvement
Date: Mon, 09 Jan 2006 17:48:21 +0200
Message-ID: <1136821701.4076.1.camel@localhost.localdomain> (raw)
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>

Ü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-IDL...
> 

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





view thread (17+ messages)

Message-ID: <1136821701.4076.1.camel@localhost.localdomain>
Permalink:  ../1136821701.4076.1.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1136821701.4076.1.camel@localhost.localdomain

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: hannu@skype.net, gsstark@mit.edu, simon@2ndquadrant.com, tgl@sss.pgh.pa.us, zhouqq@cs.toronto.edu, pgsql-hackers@postgresql.org
  Subject: Re: Stats collector performance improvement
  In-Reply-To: <1136821701.4076.1.camel@localhost.localdomain>

* 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