Skip site navigation (1) Skip section navigation (2)

Re: not all pg_stat_database fields reset after pg_stat_reset()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: tv(at)fuzzy(dot)cz, pgsql-bugs(at)postgresql(dot)org
Subject: Re: not all pg_stat_database fields reset after pg_stat_reset()
Date: 2010-12-12 20:13:08
Message-ID: 9271.1292184788@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sat, Dec 11, 2010 at 18:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

OK, applied, along with the last_autovac_time reset --- I concluded that
keeping that at the database level wouldn't be consistent, since we're
throwing it away at the table level.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2010-12-13 01:39:32
Subject: Re: BUG #5776: Unable to create view with parameter in PL/pgsql
Previous:From: Magnus HaganderDate: 2010-12-11 21:58:47
Subject: Re: not all pg_stat_database fields reset after pg_stat_reset()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group