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 35CFA11F7332 for ; Mon, 3 Apr 2006 13:40:52 -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 27557-06 for ; Mon, 3 Apr 2006 13:40:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id CA16E11F72A9 for ; Mon, 3 Apr 2006 13:40:49 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Mon, 03 Apr 2006 11:40:47 -0500 Message-Id: <443109B6.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Beta Date: Mon, 03 Apr 2006 11:40:38 -0500 From: "Kevin Grittner" To: "Jerry Sievers" , "Tom Lane" Cc: Subject: Re: pg_stat_activity showing non-existent processes References: <22874.1143340808@sss.pgh.pa.us> In-Reply-To: <22874.1143340808@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.104 required=5 tests=[AWL=0.104] X-Spam-Score: 0.104 X-Spam-Level: X-Archive-Number: 200604/30 X-Sequence-Number: 21199 >>> On Sat, Mar 25, 2006 at 8:40 pm, in message <22874.1143340808@sss.pgh.pa.us>, Tom Lane wrote: > Jerry Sievers writes: >> At any rate; I'm wondering what possible causes might be responsible >> for pg_stat_activity's underlying functions to lose track of the valid >> process list? > > It sounds like the stats collector missed a few "backend quit" > messages. This isn't real surprising: the stats messaging mechanism is > intentionally designed to drop messages under severe load, rather than > slow down backends. 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. We've been considering adding functions to get at the underlying structures to be able to retrieve it, but it would make a lot of sense (for us, anyway) to make this table accurate instead. What would be involved in that? Would it improve the accuracy of the other statistics, as well? Would anyone else be interested in something like this (probably controlled by a configuration option), or are we unique in this regard? -Kevin