Re: keeping a timestamp of the last stats reset (for a db, table and function) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: keeping a timestamp of the last stats reset (for a db, table and function)
Date
Msg-id 7626.1292727105@sss.pgh.pa.us
Whole thread Raw
In response to Re: keeping a timestamp of the last stats reset (for a db, table and function)  (Tomas Vondra <tv@fuzzy.cz>)
Responses Re: keeping a timestamp of the last stats reset (for a db, table and function)  (tv@fuzzy.cz)
Re: keeping a timestamp of the last stats reset (for a db, table and function)  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
Tomas Vondra <tv@fuzzy.cz> writes:
> I've done several small changes to the patch, namely

> - added docs for the functions (in SGML)
> - added the same thing for background writer

> So I think now it's 'complete' and I'll add it to the commit fest in a
> few minutes.

Please split this into separate patches for database-level and
table-level tracking, because I think it's highly likely that the latter
will get rejected.  We have had multiple complaints already about the
size of the stats file for databases with many tables.  I don't believe
that it's worth bloating the per-table entries even further with this
information.  Tracking reset time it per-database doesn't seem like a
problem though.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: keeping a timestamp of the last stats reset (for a db, table and function)
Next
From: Robert Haas
Date:
Subject: Re: Extensions, patch v20 (bitrot fixes) (was: Extensions, patch v19 (encoding brainfart fix))