Suppress progress reporting when creating TOAST indexes Previously, when REPACK, CLUSTER, or VACUUM FULL created a transient TOAST table, index_rebuild_count in pg_stat_progress_repack and pg_stat_progress_cluster reported 2 before any indexes on the main table had been rebuilt. This could mislead users monitoring the operation.
This happened because creating the TOAST index writes the CREATE INDEX phase to the same progress slot used for the index rebuild count of the enclosing command. Fix this by passing INDEX_CREATE_SUPPRESS_PROGRESS when creating a TOAST index, preserving the progress information of the enclosing command and keeping the count at zero until the main-table indexes are rebuilt. Author: Adam Lee <[email protected]> Reviewed-by: Fujii Masao <[email protected]> Reviewed-by: Álvaro Herrera <[email protected]> Discussion: https://postgr.es/m/aj4gJQMba0kClQmj@Mac Backpatch-through: 19 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/4b445479f9e0ea5039c782e9dab35ec9af6b6d4d Modified Files -------------- src/backend/catalog/toasting.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
