Skip to content

Commit 1766118

Browse files
committed
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
1 parent a899ec1 commit 1766118

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

doc/src/sgml/monitoring.sgml

+2
Original file line numberDiff line numberDiff line change
@@ -5716,6 +5716,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
57165716
<para>
57175717
When creating an index on a partitioned table, this column is set to
57185718
the total number of partitions on which the index is to be created.
5719+
This field is <literal>0</literal> during a <literal>REINDEX</literal>.
57195720
</para></entry>
57205721
</row>
57215722

@@ -5726,6 +5727,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
57265727
<para>
57275728
When creating an index on a partitioned table, this column is set to
57285729
the number of partitions on which the index has been completed.
5730+
This field is <literal>0</literal> during a <literal>REINDEX</literal>.
57295731
</para></entry>
57305732
</row>
57315733
</tbody>

0 commit comments

Comments
 (0)