pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: pgsql-docs@lists.postgresql.org
Subject: doc: index items for pg_stat_progress_xxx views
Date: Thu, 12 Nov 2020 17:05:10 +0900
Message-ID: <e49c2768-65d2-188a-5424-270fa29ccc84@oss.nttdata.com> (raw)

Hi,

The index items for pg_stat_progress_xxx views point to the
"Viewing Statistics" section, but not to the dedicated section
(e.g., "ANALYZE Progress Reporting") for each view. IMO this is
very inconvenient when finding the section describing each
pg_stat_progress_xxx view, from the index. So what about adding
new pointer to the section for each view in the index?
Patch attached.

BTW, other stats views have both pointers in the index.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachments:

indexterms_for_pg_stat_progress_xxx.patch (text/plain, 2.1K) download diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 98e1995453..cc48c30ef3 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -5229,6 +5229,10 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <sect2 id="analyze-progress-reporting"> <title>ANALYZE Progress Reporting</title> + <indexterm> + <primary>pg_stat_progress_analyze</primary> + </indexterm> + <para> Whenever <command>ANALYZE</command> is running, the <structname>pg_stat_progress_analyze</structname> view will contain a @@ -5442,6 +5446,10 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <sect2 id="create-index-progress-reporting"> <title>CREATE INDEX Progress Reporting</title> + <indexterm> + <primary>pg_stat_progress_create_index</primary> + </indexterm> + <para> Whenever <command>CREATE INDEX</command> or <command>REINDEX</command> is running, the <structname>pg_stat_progress_create_index</structname> view will contain @@ -5738,6 +5746,10 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <sect2 id="vacuum-progress-reporting"> <title>VACUUM Progress Reporting</title> + <indexterm> + <primary>pg_stat_progress_vacuum</primary> + </indexterm> + <para> Whenever <command>VACUUM</command> is running, the <structname>pg_stat_progress_vacuum</structname> view will contain @@ -5964,6 +5976,10 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <sect2 id="cluster-progress-reporting"> <title>CLUSTER Progress Reporting</title> + <indexterm> + <primary>pg_stat_progress_cluster</primary> + </indexterm> + <para> Whenever <command>CLUSTER</command> or <command>VACUUM FULL</command> is running, the <structname>pg_stat_progress_cluster</structname> view will @@ -6182,6 +6198,10 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <sect2 id="basebackup-progress-reporting"> <title>Base Backup Progress Reporting</title> + <indexterm> + <primary>pg_stat_progress_basebackup</primary> + </indexterm> + <para> Whenever an application like <application>pg_basebackup</application> is taking a base backup, the

view thread (13+ messages)  latest in thread

Message-ID: <e49c2768-65d2-188a-5424-270fa29ccc84@oss.nttdata.com>
Permalink:  ../e49c2768-65d2-188a-5424-270fa29ccc84@oss.nttdata.com/
Also on:    postgresql.org/message-id/e49c2768-65d2-188a-5424-270fa29ccc84@oss.nttdata.com

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, pgsql-docs@lists.postgresql.org
  Subject: Re: doc: index items for pg_stat_progress_xxx views
  In-Reply-To: <e49c2768-65d2-188a-5424-270fa29ccc84@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox