From: Tatsuo Ishii <ishii@postgresql.org>
Date: Thu, 15 Jun 2017 01:01:39 +0000 (+0900)
Subject: Fix document bug regarding read only transactions.
X-Git-Tag: REL_10_BETA2~142
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6108348c09df33773bed6e0ac762fe47bdcbb9e6;p=postgresql

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 ce67d4a5e3..72eb073621 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1824,7 +1824,7 @@ if (!triggered)
 
    <para>
     In normal operation, <quote>read-only</> transactions are allowed to
-    update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and
+    use <command>LISTEN</>, <command>UNLISTEN</>, and
     <command>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.