Postgres Pro
Downloads
Home   >   mailing lists

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 24812.1292775971@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)  (tv@fuzzy.cz)
Responses Re: keeping a timestamp of the last stats reset (for a db, table and function)  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
Tree view 
tv@fuzzy.cz writes:
> I can prepare an alternative patch, using just per-database timestamps. So
> even a reset for a single table/function would set the timestamp for the
> whole database.

That seems like quite a bizarre definition.  What I was envisioning was
that we'd track only the time of the last whole-database stats reset.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Extensions and custom_variable_classes (was: Extensions, patch v20 (bitrot fixes))
Next
From: Robert Haas
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)