Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 352769FB640 for ; Wed, 10 Oct 2007 14:22:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 03340-09 for ; Wed, 10 Oct 2007 14:22:50 -0300 (ADT) X-Greylist: delayed 00:09:52.700799 by SQLgrey-1.7.5 Received: from mail.cisx.com (mail.cisx.com [213.133.202.146]) by postgresql.org (Postfix) with ESMTP id DEB3B9F9A35 for ; Wed, 10 Oct 2007 14:22:48 -0300 (ADT) Received: from LISTINGS12 ([192.168.100.32]) by mail.cisx.com (8.13.1/8.13.1) with SMTP id l9AHMcEf014171 for ; Wed, 10 Oct 2007 18:22:44 +0100 Message-ID: <000501c80b62$2b777a10$2064a8c0@LISTINGS12> From: "Donald Fraser" To: "[ADMIN]" Subject: Timing problem wtih pg_stat_activity Date: Wed, 10 Oct 2007 18:22:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: ClamAV 0.91.2/4521/Wed Oct 10 08:58:01 2007 on mail.cisx.com X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=BAYES_50=0.001, STOX_REPLY_TYPE=0.001 X-Spam-Level: X-Archive-Number: 200710/81 X-Sequence-Number: 26995 Please ignore my previous question - I should have read the documents first! The answer is here: "When using the statistics to monitor current activity, it is important to realize that the information does not update instantaneously. Each individual server process transmits new block and row access counts to the collector just before going idle; so a query or transaction still in progress does not affect the displayed totals. Also, the collector itself emits a new report at most once per PGSTAT_STAT_INTERVAL milliseconds (500 unless altered while building the server). So the displayed information lags behind actual activity. However, current-query information collected by stats_command_string is always up-to-date." Regards Donald Fraser