X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id F336311F66FE for ; Wed, 5 Apr 2006 19:01:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 94223-05 for ; Wed, 5 Apr 2006 19:01:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id ABD4111F66EB for ; Wed, 5 Apr 2006 19:01:30 -0300 (ADT) Received: from [10.180.0.159] (unknown [66.228.91.67]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id D89D856431; Wed, 5 Apr 2006 17:01:29 -0500 (CDT) In-Reply-To: <14779.1144083156@sss.pgh.pa.us> References: <22874.1143340808@sss.pgh.pa.us> <443109B6.EE98.0025.0@wicourts.gov> <14779.1144083156@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com> Cc: "Kevin Grittner" , "Jerry Sievers" , pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: pg_stat_activity showing non-existent processes Date: Wed, 5 Apr 2006 18:00:35 -0400 To: Tom Lane X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.476 required=5 tests=[AWL=0.476] X-Spam-Score: 0.476 X-Spam-Level: X-Archive-Number: 200604/62 X-Sequence-Number: 21231 On Apr 3, 2006, at 12:52 PM, Tom Lane wrote: > "Kevin Grittner" writes: >> Is there any way to tweak this in favor of more accurate information, >> even if has a performance cost? We're finding that during normal >> operations we're not seeing most connections added to the >> pg_stat_activity table. We would like to be able to count on >> accurate >> information there. > > That's basically a non-starter because of the delay in reporting from > the stats collector process (ie, even if the information was > "completely > accurate" it'd still be stale by the time that your code gets its > hands > on it). I think you'd be talking about a complete redesign of the > stats > subsystem to be able to use it that way. BTW, there's some effort going into adding monitoring probes such as dtrace to PostgreSQL. These would likely be ideal for what you're trying to do. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461