Fix document bug regarding read only transactions.

It was explained that read only transactions (not in standby) allow to
update sequences. This had been wrong since the commit:
05d8a561ff85db1545f5768fe8d8dc9d99ad2ef7

Discussion: https://www.postgresql.org/message-id/20170614.110826.425627939780392324.t-ishii%40sraoss.co.jp

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index ebefe0f6b1c6d98b17a5d1e4027e1af6a35dcd50..4a44271484bf8e87061d493a602e4542a247633a 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1730,7 +1730,7 @@ if (!triggered)
 
    
     In normal operation, read-only transactions are allowed to
-    update sequences and to use LISTEN, UNLISTEN, and
+    use LISTEN, UNLISTEN, and
     NOTIFY, so Hot Standby sessions operate under slightly tighter
     restrictions than ordinary read-only sessions.  It is possible that some
     of these restrictions might be loosened in a future release.