From: Michael Paquier Date: Sat, 20 Feb 2021 01:25:14 +0000 (+0900) Subject: doc: Mention that partitions_{done,total} is 0 for REINDEX progress reports X-Git-Tag: REL_14_BETA1~735 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=17661188336c8cbb1783808912096932c57893a3;p=postgresql.git doc: Mention that partitions_{done,total} is 0 for REINDEX progress reports REINDEX has recently gained support for partitions, so it can be confusing to see those fields not being set. Making useful reports for for such relations is more complicated than it looks with the current set of columns available in pg_stat_progress_create_index, and this touches equally REINDEX DATABASE/SYSTEM/SCHEMA. This commit documents that those two columns are not touched during a REINDEX. Reported-by: Justin Pryzby Discussion: https://postgr.es/m/20210216064214.GI28165@telsasoft.com --- diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index c602ee44277..3513e127b78 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -5716,6 +5716,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, When creating an index on a partitioned table, this column is set to the total number of partitions on which the index is to be created. + This field is 0 during a REINDEX. @@ -5726,6 +5727,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, When creating an index on a partitioned table, this column is set to the number of partitions on which the index has been completed. + This field is 0 during a REINDEX.