Re: Report index currently being vacuumed in pg_stat_progress_vacuum

Hi,

On Thu, Sep 17, 2026 at 6:00 PM shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> v7 looks good here. Tested sequential, parallel on btree and GIN, all as the
> docs describe, including GIN reporting zero blocks and the reset
> clearing the previous index. Applies cleanly on 5e595d659fd, suites
> pass.

Thanks for testing v7 on these and for confirming the behavior matches the docs.

> > 0003 and 0004 are not things I can get much into, echoing with the
> > recent following message:
> > https://www.postgresql.org/message-id/aqqmGGS6qqm5LI0Z%40alvherre.pgsql
>
> Thanks for the pointer. I had not seen that thread, withdraw 0003 and 0004.
>
> I will work with Manu and Alvaro on the progress reporting test
> framework in that thread. This patch would make a good first user.

+1 to discussing a general approach for progress reporting tests
separately. We haven't had progress reporting tests so far, but that
doesn't mean we must not have them. One idea is to look at whether
there are any bugs or inconsistencies reported for any of the progress
reporting commands and start from there (but that's a discussion for
the other thread).

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com