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: 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 16:26:11
Message-ID: 24812.1292775971@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
tv(at)fuzzy(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-12-19 16:28:03
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Previous:From: Tom LaneDate: 2010-12-19 16:21:51
Subject: Re: Extensions and custom_variable_classes (was: Extensions, patch v20 (bitrot fixes))

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