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 4630.1292786914@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)  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
Tomas Vondra <tv@fuzzy.cz> writes:
> Dne 19.12.2010 17:26, Tom Lane napsal(a):
>> 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.

> Well, but that does not quite work. I need is to know whether the
> snapshot is 'consistent' i.e. whether I can compare it to the previous
> snapshot and get meaningful results (so that I can perform some analysis
> on the difference).

Oh, I see.  Yeah, if that's what you want it for then partial resets
have to change the timestamp too.  I guess if we are careful to document
it properly, this won't be too horrid.
        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: Andrew Dunstan
Date:
Subject: Re: MingW and MiniDumps