On Sat, Dec 11, 2010 at 18:31, Tom Lane <t...@sss.pgh.pa.us> wrote: > t...@fuzzy.cz writes: >> After calling pg_stat_reset, some of the database stats fields are not >> actually reset, the value is preserved. I've found the bug is actually in >> pgstat_recv_resetcounter function, where only some of the >> PgStat_StatDBEntry fields are reset to 0. > >> This is true for those 6 fields: > >> n_tuples_returned >> n_tuples_fetched >> n_tuples_inserted >> n_tuples_updated >> n_tuples_deleted >> last_autovac_time > > Hmm. I think that not resetting the n_tuples_xxx fields was simply an > oversight in Magnus' patch that added them, > http://archives.postgresql.org/pgsql-committers/2007-03/msg00144.php > Magnus, was this intentional by any chance?
Nope, not that I can recall. Looks like an oversight. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
