| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
| Date: | 2015-06-30 08:32:44 |
| Message-ID: | CANP8+jJPt3qru9h1N2k2_KKjjSuXDYgyX6BdW3XUKBEG+ShgKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30 June 2015 at 08:52, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I though about the possibilities of progress visualization - and one
> possibility is one or two special column in pg_stat_activity table - this
> info can be interesting for VACUUM started by autovacuum too.
>
Yes, I suggest just a single column on pg_stat_activity called pct_complete
trace_completion_interval = 5s (default)
Every interval, we report the current % complete for any operation that
supports it. We just show NULL if the current operation has not reported
anything or never will.
We do this for VACUUM first, then we can begin adding other operations as
we work out how (for that operation).
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2015-06-30 08:44:52 | Re: [PROPOSAL] VACUUM Progress Checker. |
| Previous Message | Amit Kapila | 2015-06-30 08:31:42 | Re: Reducing ClogControlLock contention |