diff options
| author | Michael Paquier | 2021-02-20 01:25:14 +0000 |
|---|---|---|
| committer | Michael Paquier | 2021-02-20 01:25:14 +0000 |
| commit | 17661188336c8cbb1783808912096932c57893a3 (patch) | |
| tree | 7ea0e00ff02f4775c630eb3dde1aa346bca7ae25 | |
| parent | a899ec1cb23eb3c4a94648f18a9408e5316d32a4 (diff) | |
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
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index c602ee4427..3513e127b7 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, <para> 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 <literal>0</literal> during a <literal>REINDEX</literal>. </para></entry> </row> @@ -5726,6 +5727,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <para> 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 <literal>0</literal> during a <literal>REINDEX</literal>. </para></entry> </row> </tbody> |