pgsql: Fix progress reporting of REINDEX CONCURRENTLY - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Fix progress reporting of REINDEX CONCURRENTLY
Date
Msg-id E1kN83Q-0000MG-3O@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix progress reporting of REINDEX CONCURRENTLY

This addresses a couple of issues with the so-said subject:
- Report the correct parent relation with the index actually being
rebuilt or validated.  Previously, the command status remained set to
the last index created for the progress of the index build and
validation, which would be incorrect when working on a table that has
more than one index.
- Use the correct phase when waiting before the drop of the old
indexes.  Previously, this was reported with the same status as when
waiting before the old indexes are marked as dead.

Author: Matthias van de Meent, Michael Paquier
Discussion: https://postgr.es/m/CAEze2WhqFgcwe1_tv=sFYhLWV2AdpfukumotJ6JNcAOQs3jufg@mail.gmail.com
Backpatch-through: 12

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e66bcfb4c66ebc97020b1f7484b1529bd7993f23

Modified Files
--------------
src/backend/commands/indexcmds.c | 70 +++++++++++++++++++++++++++++++---------
1 file changed, 54 insertions(+), 16 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Add for_each_from, to simplify loops starting from non-first lis
Next
From: Fujii Masao
Date:
Subject: pgsql: Archive timeline history files in standby if archive_mode is set