The replication status values in pg_stat_replication was changed to

lowercase earlier, but documentation was not updated. Update the docs.

Fujii Masao

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 67e722f7572e6130c1325c201cbce1450aca52f7..4b351695a495d6f936c8b3bb8d5395b6d85cb7be 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2103,7 +2103,7 @@ SET ENABLE_SEQSCAN TO OFF;
         this standby server confirms receipt of their data.
         The synchronous standby will be the first standby named in this list
         that is both currently connected and streaming data in real-time
-        (as shown by a state of STREAMING in the
+        (as shown by a state of streaming in the
         
         pg_stat_replication view).
         Other standby servers appearing later in this list represent potential

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index c1680301d3f06c91472477b6c47b8d7a4eee56f3..8bcdc07a763a889058a0dc1bd4ad95abca496e0b 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1088,14 +1088,14 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
 
    
     When a standby first attaches to the primary, it will not yet be properly
-    synchronized. This is described as CATCHUP mode. Once
+    synchronized. This is described as catchup mode. Once
     the lag between standby and primary reaches zero for the first time
-    we move to real-time STREAMING state.
+    we move to real-time streaming state.
     The catch-up duration may be long immediately after the standby has
     been created. If the standby is shut down, then the catch-up period
     will increase according to the length of time the standby has been down.
     The standby is only able to become a synchronous standby
-    once it has reached STREAMING state.
+    once it has reached streaming state.