From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
---|---|
To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Displaying accumulated autovacuum cost |
Date: | 2011-08-18 01:23:07 |
Message-ID: | 4E4C697B.1020109@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/17/2011 07:42 PM, Euler Taveira de Oliveira wrote:
> I don't like exposing this information only on title processes. It
> would be difficult for client apps (for example, PGAdmin) to track
> this kind of information and it is restricted to local access. I'm not
> objecting to display this information in process title; I'm just
> saying that that information should be exposed in functions (say
> pg_stat_get_vacuum_[hit|miss|dirty]) too.
I tend to build the simplest possible thing that is useful enough to
work. The data is getting stored and shown now, where it wasn't
before. If it's possible to expose that in additional ways later too,
great. The big step up for this information is to go from
"unobtainable" to "obtainable". I'd prefer not to add a quest for
"easily obtainable" to the requirements until that big jump is made, for
fear it will cause nothing to get delivered.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2011-08-18 01:43:21 | Re: Online base backup from the hot-standby |
Previous Message | Euler Taveira de Oliveira | 2011-08-17 23:42:48 | Re: Displaying accumulated autovacuum cost |