From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Greg Smith <greg(at)2ndquadrant(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Displaying accumulated autovacuum cost |
Date: | 2011-08-18 15:13:13 |
Message-ID: | CA+TgmoYDnoqw-Ghm5wfE0=3i44icg_eFANegRYavf+tY39qNAQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 18, 2011 at 10:54 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On tor, 2011-08-18 at 08:39 +0200, Magnus Hagander wrote:
>> Also, unrelated to that, wouldn't this information be interesting for
>> non-autovacuum queries as well?
>
> Last year we were discussing some details on progress reporting, and
> some people suggested that instead of printing a single percentage, we
> should let each type of activity print out whatever metrics it has that
> would allow an experienced DBA to track the progress. Â Effectively, this
> is what this patch is trying to do.
>
> So how about adding a column to pg_stat_activity, progress_metrics or
> something like that, and add that information there.
That might be a good way to go. I don't think we want something like
pg_stat_all_tables for this, because it seems that Greg's use case is
to be able to see how a *particular* autovacuum process is doing
*while it's running*, not to look at aggregate statistics over time.
Putting it in pg_stat_activity would be good for that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2011-08-18 15:14:40 | Re: Displaying accumulated autovacuum cost |
Previous Message | Peter Eisentraut | 2011-08-18 14:54:31 | Re: Displaying accumulated autovacuum cost |