Re: Report index currently being vacuumed in pg_stat_progress_vacuum

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>
Subject: Re: Report index currently being vacuumed in pg_stat_progress_vacuum
Date: 2026-10-01 03:18:23
Message-ID: CAGRkXqRH8Wh50cVfvwxyZfctTjzCN-j9xCWOSmk9T-0fbUGBXw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I've looked at v7, and my main comment is that this is bloated in
> terms of docs and comments.

+1 for v8. I tested serial, parallel and parallel autovacuum. The view
matches the new docs.

> + * they report progress for the index they are processing.
>
> This reads a bit weird as well..

Maybe this:

* Parallel vacuum workers perform only index vacuum or index cleanup,
* so their progress row only shows the phase and the current index.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-10-01 03:25:07 Re: Session in aborted transaction misses effective_wal_level change
Previous Message Grigorev Jurij 2026-10-01 03:18:11 Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ