From e4101c7f192ab82866e5593d5d913a19595ca10d Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Mon, 20 May 2019 19:04:15 -0500 Subject: [PATCH v5 08/12] Consistent language: contains --- doc/src/sgml/monitoring.sgml | 46 ++++++++++++++++++++++---------------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index df5df62..964c8c5 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1976,9 +1976,9 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_replication view will contain one row - per WAL sender process, showing statistics about replication to that - sender's connected standby server. Only directly connected standbys are + The pg_stat_replication view contains one row + per WAL sender process, showing statistics about replication to the + associated standby server. Only directly connected standbys are listed; no information is available about downstream standby servers. @@ -2126,7 +2126,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_wal_receiver view will contain only + The pg_stat_wal_receiver view contains only one row, showing statistics about the WAL receiver from that receiver's connected server. @@ -2198,8 +2198,8 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_subscription view will contain one - row per subscription for main worker (with null PID if the worker is + The pg_stat_subscription view contains one + row per subscription for the main worker (with null PID if the worker is not running), and additional rows for workers handling the initial data copy of the subscribed tables. @@ -2281,9 +2281,9 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_ssl view will contain one row per + The pg_stat_ssl view contains one row per backend or WAL sender process, showing statistics about SSL usage on - this connection. It can be joined to pg_stat_activity + the associated connection. It can be joined to pg_stat_activity or pg_stat_replication on the pid column to get more details about the connection. @@ -2330,8 +2330,8 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_gssapi view will contain one row per - backend, showing information about GSSAPI usage on this connection. It can + The pg_stat_gssapi view contains one row per + backend, showing information about GSSAPI usage on the associated connection. It can be joined to pg_stat_activity or pg_stat_replication on the pid column to get more details about the @@ -2632,7 +2632,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_database view will contain one row + The pg_stat_database view contains one row for each database in the cluster, plus one for shared objects, showing database-wide statistics. @@ -2694,7 +2694,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_database_conflicts view will contain + The pg_stat_database_conflicts view contains one row per database, showing database-wide statistics about query cancels occurring due to conflicts with recovery on standby servers. This view will only contain information on standby servers, since @@ -2835,7 +2835,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_all_tables view will contain + The pg_stat_all_tables view contains one row for each table in the current database (including TOAST tables), showing statistics about accesses to that specific table. The pg_stat_user_tables and @@ -2902,7 +2902,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_all_indexes view will contain + The pg_stat_all_indexes view contains one row for each index in the current database, showing statistics about accesses to that specific index. The pg_stat_user_indexes and @@ -3012,7 +3012,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_statio_all_tables view will contain + The pg_statio_all_tables view contains one row for each table in the current database (including TOAST tables), showing statistics about I/O on that specific table. The pg_statio_user_tables and @@ -3073,7 +3073,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_statio_all_indexes view will contain + The pg_statio_all_indexes view contains one row for each index in the current database, showing statistics about I/O on that specific index. The pg_statio_user_indexes and @@ -3124,7 +3124,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_statio_all_sequences view will contain + The pg_statio_all_sequences view contains one row for each sequence in the current database, showing statistics about I/O on that specific sequence. @@ -3178,7 +3178,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i - The pg_stat_user_functions view will contain + The pg_stat_user_functions view contains one row for each tracked function, showing statistics about executions of that function. The parameter controls exactly which functions are tracked. @@ -3490,7 +3490,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, Whenever CREATE INDEX or REINDEX is running, the - pg_stat_progress_create_index view will contain + pg_stat_progress_create_index view contains one row for each backend that is currently creating indexes. The tables below describe the information that will be reported and provide information about how to interpret it. @@ -3653,7 +3653,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, The index is being built by code specific to the access method, and if it supports progress reporting, this indicates the method's subphase. blocks_total and blocks_done - will contain progress data, as may + contain progress data, as may tuples_total and tuples_done. @@ -3738,7 +3738,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, VACUUM Progress Reporting - The pg_stat_progress_vacuum view will contain one + The pg_stat_progress_vacuum view contains one row for each backend that is running VACUUM, including autovacuum worker processes. The tables below describe the information @@ -3930,8 +3930,8 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, CLUSTER Progress Reporting - The pg_stat_progress_cluster view will contain a - row for each backend that is running either + The pg_stat_progress_cluster view contains a + row for each backend running CLUSTER or VACUUM FULL. The tables below describe the information that will be reported and provide information about how to interpret it. -- 2.7.4