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 115B711F6628 for ; Mon, 3 Apr 2006 13:52:40 -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 29784-06 for ; Mon, 3 Apr 2006 13:52:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id F0CED11F6544 for ; Mon, 3 Apr 2006 13:52:37 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k33GqaWm014782; Mon, 3 Apr 2006 12:52:36 -0400 (EDT) To: "Kevin Grittner" cc: "Jerry Sievers" , pgsql-admin@postgresql.org Subject: Re: pg_stat_activity showing non-existent processes In-reply-to: <443109B6.EE98.0025.0@wicourts.gov> References: <22874.1143340808@sss.pgh.pa.us> <443109B6.EE98.0025.0@wicourts.gov> Comments: In-reply-to "Kevin Grittner" message dated "Mon, 03 Apr 2006 11:40:38 -0500" Date: Mon, 03 Apr 2006 12:52:36 -0400 Message-ID: <14779.1144083156@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.114 required=5 tests=[AWL=0.114] X-Spam-Score: 0.114 X-Spam-Level: X-Archive-Number: 200604/31 X-Sequence-Number: 21200 "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. Having said that, though, I'd be pretty surprised if the stats subsystem was dropping more than a small fraction of messages --- I would think that could only occur under very heavy load, and if that's your normal operating state then it's time to upgrade your hardware ;-). Maybe you should investigate a bit more closely to find out why it's dropping so much. regards, tom lane