Re: Add index scan progress to pg_stat_progress_vacuum

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

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

Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Andres Freund <andres@anarazel.de>, "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>, vignesh C <vignesh21@gmail.com>, Nathan Bossart <nathandbossart@gmail.com>, Robert Haas <robertmhaas@gmail.com>, "Bossart, Nathan" <bossartn@amazon.com>, Peter Geoghegan <pg@bowt.ie>, Justin Pryzby <pryzby@telsasoft.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2023-04-12T04:46:41Z

Lists: pgsql-hackers

Attachments

v29-0001-Report-index-vacuum-progress.patch (text/x-diff) patch v29-0001

On Mon, Apr 10, 2023 at 07:20:42PM +0000, Imseih (AWS), Sami wrote:
> See v28 addressing the comments.

This should be OK (also checked the code paths where the reports are
added).  Note that the patch needed a few adjustments for its
indentation.
--
Michael

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