pgsql: Use pgstat_progress_update_multi_param() where possible

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use pgstat_progress_update_multi_param() where possible
Date: 2021-02-22 05:22:03
Message-ID: E1lE3fX-0006OH-MR@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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: https://postgr.es/m/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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2021-02-22 07:09:26 pgsql: Improve new hash partition bound check error messages
Previous Message Thomas Munro 2021-02-22 01:45:16 pgsql: Remove outdated reference to RAID spindles.