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

Re: keeping a timestamp of the last stats reset (for a db, table and function)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: keeping a timestamp of the last stats reset (for a db, table and function)
Date: 2010-12-19 19:28:34
Message-ID: 4630.1292786914@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tomas Vondra <tv(at)fuzzy(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-12-19 19:58:30
Subject: Re: MingW and MiniDumps
Previous:From: Tomas VondraDate: 2010-12-19 19:27:00
Subject: Re: keeping a timestamp of the last stats reset (for a db, table and function)

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