Re: [PROPOSAL] VACUUM Progress Checker.

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,

http://www.postgresql.org/message-id/13072.1284826206@sss.pgh.pa.us

>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(at)2ndquadrant(dot)com> wrote:

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