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

From Syed, Rahila
Subject Re: [PROPOSAL] VACUUM Progress Checker.
Date
Msg-id C3C878A2070C994B9AE61077D46C38468815E7AA@MAIL703.KDS.KEANE.COM
Whole thread Raw
In response to Re: [PROPOSAL] VACUUM Progress Checker.  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [PROPOSAL] VACUUM Progress Checker.
List pgsql-hackers
Hello,

>When we're in Phase2 or 3, don't we need to report the number of total page scanned or percentage of how many table
pagesscanned, as well? 
The total heap pages scanned need to be reported with phase 2 or 3. Complete progress report need to have numbers from
eachphase when applicable.  

> Phase 1. Report 2 integer counters: heap pages scanned and total heap
> pages,
> 1 float counter: percentage_complete and progress message.
> Phase 2. Report 2 integer counters: index pages scanned and total
> index pages(across all indexes) and progress message.
> Phase 3. 1 integer counter: heap pages vacuumed.

Sorry for being unclear here. What I meant to say is, each phase of a command will correspond to a slot in
COMMAND_NUM_SLOTS.Each phase will be a separate array element and  
will comprise of n integers, n floats, string. So , in the view reporting progress, VACUUM command can have 3 entries
onefor each phase.  

Thank you,
Rahila Syed



______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: WIP: Rework access method interface
Next
From: Robert Haas
Date:
Subject: Re: Asynchronous execution on FDW