pgsql: Fix progress reporting of REINDEX CONCURRENTLY

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема pgsql: Fix progress reporting of REINDEX CONCURRENTLY
Дата
Msg-id E1kN83Q-0000MH-40@gemulon.postgresql.org
обсуждение исходный текст
Список 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
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/1aedaba78aa8617b24b7a703abd1359f9d78f62a

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


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Add for_each_from, to simplify loops starting from non-first lis
Следующее
От: Fujii Masao
Дата:
Сообщение: pgsql: Archive timeline history files in standby if archive_mode is set