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.m.guerrero@xxxxxxxxxxx> Center for Information Technology Services University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
