From c880096dc1e14b62610aa34bc98db226fa134260 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Tue, 4 Jun 2019 09:16:02 +0200 Subject: Add command column to pg_stat_progress_create_index This allows determining which command is running, similar to pg_stat_progress_cluster. Discussion: https://www.postgresql.org/message-id/flat/f0e56b3b-74b7-6cbc-e207-a5ed6bee18dc%402ndquadrant.com --- doc/src/sgml/monitoring.sgml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'doc/src') diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 570ac5e06f7..bf72d0c3031 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3534,6 +3534,15 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, OID of the index being created or reindexed. During a non-concurrent CREATE INDEX, this is 0. + + command + text + + The command that is running: CREATE INDEX, + CREATE INDEX CONCURRENTLY, + REINDEX, or REINDEX CONCURRENTLY. + + phase text @@ -3965,7 +3974,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, command text - The command that is running. Either CLUSTER or VACUUM FULL. + The command that is running. Either CLUSTER or VACUUM FULL. -- cgit v1.2.3