Re: Add index scan progress to pg_stat_progress_vacuum

Sami Imseih <simseih@amazon.com>

From: "Imseih (AWS), Sami" <simseih@amazon.com>

To: Masahiko Sawada <sawada.mshk@gmail.com>, Nathan Bossart <nathandbossart@gmail.com>

Cc: Peter Geoghegan <pg@bowt.ie>, "Bossart, Nathan" <bossartn@amazon.com>, Justin Pryzby <pryzby@telsasoft.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2022-03-14T22:21:50Z

Lists: pgsql-hackers

Attachments

v8-0001-Add-infrastructure-for-parallel-progress-reportin.patch (application/octet-stream) patch v8-0001
v8-0002-Show-progress-for-index-vacuums.patch (application/octet-stream) patch v8-0002
v8-0003-Expose-indexes-being-processed-in-a-VACUUM-operat.patch (application/octet-stream) patch v8-0003
v8-0004-Rename-index_vacuum_count-in-pg_stat_pogress_vacu.patch (application/octet-stream) patch v8-0004

Attaching a v8 due to naming convention fixes and one slight change in where index_processed is set after all indexes are vacuumed.

s/indexes_completed/indexes_processed/

--
Sami Imseih
Amazon Web Services

Commits

Report index vacuum progress.
- 46ebdfe164c6 17.0 landed
Add new parallel message type to progress reporting.
- f1889729dd3a 17.0 landed
Remove MaxBackends variable in favor of GetMaxBackends() function.
- aa64f23b0292 15.0 cited