Postgres Pro
Downloads
Home   >   mailing lists

Re: [PROPOSAL] VACUUM Progress Checker. - Mailing list pgsql-hackers

From Rahila Syed
Subject Re: [PROPOSAL] VACUUM Progress Checker.
Date
Msg-id CAH2L28v1QEmen11375C8d1iTxufgWJuDDZ8Dp6dJFVsGcYhiqQ@mail.gmail.com
Whole thread Raw
In response to Re: [PROPOSAL] VACUUM Progress Checker.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: [PROPOSAL] VACUUM Progress Checker.
List pgsql-hackers
Tree view
Hello,

Thank you for suggestions. 

>Yes, I suggest just a single column on pg_stat_activity called pct_complete

Reporting remaining time also can be crucial to make decisions regarding continuing or aborting VACUUM. 
The same has been suggested  in  the thread below,


>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).

Thank you for explaining. This design seems good to me except, adding more than one columns(percent_complete, remaining_time) if required to pg_stat_activity can be less user intuitive than having a separate view for VACUUM. 

-Rahila Syed



















On Tue, Jun 30, 2015 at 2:02 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 30 June 2015 at 08:52, Pavel Stehule <pavel.stehule@gmail.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/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Expending the use of xlog_internal.h's macros
Next
From: Rahila Syed
Date:
Subject: Re: [PROPOSAL] VACUUM Progress Checker.