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

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
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: 2011-01-30 22:22:50
Message-ID: AANLkTimrp8FjHoTCZygxZzriZXxdOf+tqdy3gxRpc6Lc@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Dec 23, 2010 at 2:41 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
>>> OK, so here goes the simplified patch - it tracks one reset timestamp
>>> for a background writer and for each database.
>>
>> I think you forgot the attachment.
>
> Yes, I did. Thanks!

This patch no longer applies.  Please update.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Jan UrbaƄskiDate: 2011-01-30 22:23:39
Subject: Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)
Previous:From: Tom LaneDate: 2011-01-30 22:14:50
Subject: Re: WIP: RangeTypes

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