From: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
---|---|
To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_stat_reset() not resetting all statistics counters |
Date: | 2009-07-15 12:39:38 |
Message-ID: | 4A5DCE0A.1000807@usit.uio.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Brad Nicholson wrote:
> On Wed, 2009-07-15 at 14:13 +0200, Rafael Martinez wrote:
>> Hello
>>
>> Should not the execution of pg_stat_reset() reset *all* statistics
>> counters everywhere in the database?
>
> It only resets the stats for the current database, not the cluster wide
> stats - pg_database is cluster wide.
>
Jepp, thanks, but this explanation is an 'internal' explanation.
A *normal* user sees a row per database when running pg_stat_database
and that all the columns have values per database.
It looks wrong and it is not logic if half of the columns for a database
returned by pg_stat_database get a new value and the other half still
have old values after running pg_stat_reset(). Don't you think?
Specially when values associated to inserts, updates, deleted, etc in
pg_stat_user_* get a new value after running pg_stat_reset(). In my
humble opinion this not a consistent behavior.
regards,
--
Rafael Martinez, <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
Center for Information Technology Services
University of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
From | Date | Subject | |
---|---|---|---|
Next Message | Abraham, Danny | 2009-07-15 15:07:48 | initdb --locale=LATIN1 fails on Windows |
Previous Message | Rafael Martinez | 2009-07-15 12:25:23 | Re: pg_stat_reset() not resetting all statistics counters |