1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00

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
This commit is contained in:
Peter Eisentraut
2019-06-04 09:16:02 +02:00
parent 041a2642e5
commit c880096dc1
7 changed files with 40 additions and 2 deletions

View File

@ -3534,6 +3534,15 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry>OID of the index being created or reindexed. During a
non-concurrent <command>CREATE INDEX</command>, this is 0.</entry>
</row>
<row>
<entry><structfield>command</structfield></entry>
<entry><type>text</type></entry>
<entry>
The command that is running: <literal>CREATE INDEX</literal>,
<literal>CREATE INDEX CONCURRENTLY</literal>,
<literal>REINDEX</literal>, or <literal>REINDEX CONCURRENTLY</literal>.
</entry>
</row>
<row>
<entry><structfield>phase</structfield></entry>
<entry><type>text</type></entry>
@ -3965,7 +3974,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<entry><structfield>command</structfield></entry>
<entry><type>text</type></entry>
<entry>
The command that is running. Either CLUSTER or VACUUM FULL.
The command that is running. Either <literal>CLUSTER</literal> or <literal>VACUUM FULL</literal>.
</entry>
</row>
<row>