Magnus Hagander <[email protected]> writes:
> On Sat, Dec 11, 2010 at 18:31, Tom Lane <[email protected]> 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

-- 
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Reply via email to