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 5FE4C9DCBB0 for ; Sun, 26 Mar 2006 20:32:33 -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 18901-03 for ; Sun, 26 Mar 2006 20:32:36 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from prod01.jerrysievers.com (adsl-64-118-249-70.netrox.net [64.118.249.70]) by postgresql.org (Postfix) with ESMTP id BB6799DC9A7 for ; Sun, 26 Mar 2006 20:32:30 -0400 (AST) Received: (from gsievers@localhost) by prod01.jerrysievers.com (8.11.0/8.11.0) id k2R0WTk09545; Sun, 26 Mar 2006 19:32:29 -0500 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: pg_stat_activity showing non-existent processes References: <22874.1143340808@sss.pgh.pa.us> From: Jerry Sievers Date: 26 Mar 2006 19:32:29 -0500 In-Reply-To: Tom Lane's message of "Sat, 25 Mar 2006 21:40:08 -0500" Message-ID: Lines: 38 X-Mailer: Gnus v5.7/Emacs 20.7 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.091 required=5 tests=[AWL=0.091] X-Spam-Score: 0.091 X-Spam-Level: X-Archive-Number: 200603/281 X-Sequence-Number: 21038 Tom Lane writes: > 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. Tom, I appreciate your comments on this. > 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. This machine is going to be upgraded to 8.1 ASAP. In the meantime, I may adjust the cron run time for the batch job that terminates these sessions in case it's running concurrently with other batch traffic. I believe the thing runs hourly at the 00 minute and this may likely be a time that we're kicking off all sorts of other jobs too. > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- ------------------------------------------------------------------------------- Jerry Sievers 305 854-3001 (home) WWW ECommerce Consultant 305 321-1144 (mobile http://www.JerrySievers.com/