To: pgsql-docs@lists.postgresql.org
From: Maksim Milyutin <milyutinma@gmail.com>
Subject: Typo in description of replay_lag attribute in pg_stat_replication
 view
Message-ID: <27b3b80c-3615-2d76-02c5-44566b53136c@gmail.com>
Date: Mon, 3 Dec 2018 18:18:30 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------D8DCA468A7B2CE2DE9C07B82"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------D8DCA468A7B2CE2DE9C07B82
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello!


I have noticed that in description of *flush_lag* in pg_stat_replication 
view 
(https://www.postgresql.org/docs/current/monitoring-stats.html#PG-STAT-REPLICATION-VIEW) 
there exists unknown value of synchronous_commit parameter - 
*remote_flush*. I think it was meant to use the value *on*.

Small patch is attached.

-- 
Regards, Maksim Milyutin


--------------D8DCA468A7B2CE2DE9C07B82
Content-Type: text/x-patch;
 name="flush_lag_fix.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="flush_lag_fix.patch"

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 4164d84..33869be 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -1856,7 +1856,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
       notification that this standby server has written and flushed it
       (but not yet applied it).  This can be used to gauge the delay that
       <literal>synchronous_commit</literal> level
-      <literal>remote_flush</literal> incurred while committing if this
+      <literal>on</literal> incurred while committing if this
       server was configured as a synchronous standby.</entry>
     </row>
     <row>

--------------D8DCA468A7B2CE2DE9C07B82--