diff options
Diffstat (limited to 'doc/src/sgml/monitoring.sgml')
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 79ca45a1563..9ff5eea0388 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -802,7 +802,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser <row> <entry><structfield>backend_type</structfield></entry> <entry><type>text</type></entry> - <entry>Type of current backend. Possible types are + <entry>Type of current backend. Possible types are <literal>autovacuum launcher</>, <literal>autovacuum worker</>, <literal>background worker</>, <literal>background writer</>, <literal>client backend</>, <literal>checkpointer</>, @@ -1827,7 +1827,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i the standby to catch up with the sending server assuming the current rate of replay. Such a system would show similar times while new WAL is being generated, but would differ when the sender becomes idle. In - particular, when the standby has caught up completely, + particular, when the standby has caught up completely, <structname>pg_stat_replication</structname> shows the time taken to write, flush and replay the most recent reported WAL location rather than zero as some users might expect. This is consistent with the goal of |