Re: not all pg_stat_database fields reset after pg_stat_reset()
От | Magnus Hagander |
---|---|
Тема | Re: not all pg_stat_database fields reset after pg_stat_reset() |
Дата | |
Msg-id | AANLkTik5A2EPt2c7npJArnSJK3cwUoA5rQJqdpeR3MOO@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: not all pg_stat_database fields reset after pg_stat_reset() (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: not all pg_stat_database fields reset after pg_stat_reset()
|
Список | pgsql-bugs |
On Sat, Dec 11, 2010 at 18:31, Tom Lane <tgl@sss.pgh.pa.us> wrote: > tv@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. =A0I 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. --=20 =A0Magnus Hagander =A0Me: http://www.hagander.net/ =A0Work: http://www.redpill-linpro.com/
В списке pgsql-bugs по дате отправления: