> My point is whether we should show > indexes_total throughout the vacuum execution (even also in not > relevant phases such as heap scanning/vacuum/truncation).
That is a good point. We should only show indexes_total and indexes_completed only during the relevant phases. V21 addresses this along with a documentation fix. indexes_total and indexes_completed can only be a value > 0 while in the "vacuuming indexes" or "cleaning up indexes" phases of vacuum. Indexes_total is set to 0 at the start of the index vacuum cycle or index cleanups and set back to 0, along with indexes_completed, at the end of the index vacuum cycle and index cleanups Also, for the progress updates in vacuumlazy.c that should be done atomically, I made a change to use pgstat_progress_update_multi_param. Regards, -- Sami Imseih Amazon Web Services: https://aws.amazon.com
v21-0001-Add-2-new-columns-to-pg_stat_progress_vacuum.-Th.patch
Description: v21-0001-Add-2-new-columns-to-pg_stat_progress_vacuum.-Th.patch
