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 118349DD54B for ; Sat, 25 Mar 2006 22:40:08 -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 75858-02 for ; Sat, 25 Mar 2006 22:40:12 -0400 (AST) 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 BD7C79DD200 for ; Sat, 25 Mar 2006 22:40:05 -0400 (AST) 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 k2Q2e8cf022875; Sat, 25 Mar 2006 21:40:08 -0500 (EST) To: Jerry Sievers cc: pgsql-admin@postgresql.org Subject: Re: pg_stat_activity showing non-existent processes In-reply-to: References: Comments: In-reply-to Jerry Sievers message dated "25 Mar 2006 11:08:03 -0500" Date: Sat, 25 Mar 2006 21:40:08 -0500 Message-ID: <22874.1143340808@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: 200603/265 X-Sequence-Number: 21022 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. We recently put in a filter that prevents reporting pg_stat_activity lines for backends that are dead according to the up-to-date list in shared memory. I don't think that's in 8.0.3 though. regards, tom lane