diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml index 7d816c87c60..c8fcebc1612 100644 --- a/doc/src/sgml/ref/analyze.sgml +++ b/doc/src/sgml/ref/analyze.sgml @@ -273,6 +273,12 @@ ANALYZE [ VERBOSE ] [ table_and_columns + + + Each backend running ANALYZE will report its progress + in the pg_stat_progress_analyze view. See + for details. + @@ -291,6 +297,7 @@ ANALYZE [ VERBOSE ] [ table_and_columns + diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml index 5dd21a0189f..0d9720fd8e6 100644 --- a/doc/src/sgml/ref/cluster.sgml +++ b/doc/src/sgml/ref/cluster.sgml @@ -192,6 +192,11 @@ CLUSTER [VERBOSE] are periodically reclustered. + + Each backend running CLUSTER will report its progress + in the pg_stat_progress_cluster view. See + for details. + @@ -242,6 +247,7 @@ CLUSTER index_name ON + diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 0fca6583af6..aea2eb8386a 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -82,6 +82,12 @@ COPY { table_name [ ( + + + Each backend running COPY will report its progress + in the pg_stat_progress_copy view. See + for details. + @@ -1052,4 +1058,12 @@ COPY [ BINARY ] table_name [ WITH NULL AS 'null_string' ] + + + See Also + + + + + diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index 965dcf472ca..51b4d579399 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -867,6 +867,12 @@ Indexes: will interpret it as USING gist, to simplify conversion of old databases to GiST. + + + Each backend running CREATE INDEX will report its + progress in the pg_stat_progress_create_index + view. See for details. + @@ -980,6 +986,7 @@ CREATE INDEX CONCURRENTLY sales_quantity_index ON sales_table (quantity); + diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index 5754ad5aa6b..14cc88a8522 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -904,6 +904,7 @@ PostgreSQL documentation + diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index b22d39eba92..ff4dba8c363 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -495,6 +495,12 @@ Indexes: is reindexed concurrently, those indexes will be skipped. (It is possible to reindex such indexes without the CONCURRENTLY option.) + + + Each backend running REINDEX will report its progress + in the pg_stat_progress_create_index view. See + for details. + @@ -553,6 +559,7 @@ REINDEX TABLE CONCURRENTLY my_broken_table; + diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index 4bb624979bd..bb1c0f8fb6f 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -393,6 +393,15 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ . + + Each backend running VACUUM without the + FULL option will report its progress in the + pg_stat_progress_vacuum view. Backends running + VACUUM FULL will instead report their progress in the + pg_stat_progress_cluster view. See + and + for details. + @@ -422,6 +431,8 @@ VACUUM (VERBOSE, ANALYZE) onek; + +