From: Donald Fraser <postgres@kiwi-fraser.net>
To: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Timing problem wtih pg_stat_activity
Date: Wed, 10 Oct 2007 18:22:38 +0100
Message-ID: <000501c80b62$2b777a10$2064a8c0@LISTINGS12> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: postgres@kiwi-fraser.net
Subject: Re: Timing problem wtih pg_stat_activity
In-Reply-To: <000501c80b62$2b777a10$2064a8c0@LISTINGS12>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox