pgsql: Use pgstat_progress_update_multi_param() where possible

Started by Michael Paquierover 5 years ago1 messagescomitters

michael@paquier.xyz

over 5 years ago

Use pgstat_progress_update_multi_param() where possible

This commit changes one code path in REINDEX INDEX and one code path
in CREATE INDEX CONCURRENTLY to report the progress of each operation
using pgstat_progress_update_multi_param() rather than
multiple calls to pgstat_progress_update_param(). This has the
advantage to make the progress report more consistent to the end-user
without impacting the amount of information provided.

Author: Bharath Rupireddy
Discussion: /messages/by-id/CALj2ACV5zW7GxD8D_tyO==bcj6ZktQchEKWKPBOAGKiLhAQo=w@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/92942642788c9d73e4c090ee0a77603f7afbc1d7

Modified Files
--------------
src/backend/catalog/index.c | 14 ++++++++++----
src/backend/commands/indexcmds.c | 19 ++++++++++++++-----
2 files changed, 24 insertions(+), 9 deletions(-)