Fix document bug regarding read only transactions.

tatsuo-ishii · tatsuo-ishii · commit 6108348c09df · 2017-06-15T10:01:39.000+09:00
It was explained that read only transactions (not in standby) allow to update sequences. This had been wrong since the commit: 05d8a56 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
@@ -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.

Original file line number	Diff line number	Diff line change
`@@ -1824,7 +1824,7 @@ if (!triggered)`
`1824`	`1824`
`1825`	`1825`	`<para>`
`1826`	`1826`	`In normal operation, <quote>read-only</> transactions are allowed to`
`1827`		`- update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and`
	`1827`	`+ use <command>LISTEN</>, <command>UNLISTEN</>, and`
`1828`	`1828`	`<command>NOTIFY</>, so Hot Standby sessions operate under slightly tighter`
`1829`	`1829`	`restrictions than ordinary read-only sessions. It is possible that some`
`1830`	`1830`	`of these restrictions might be loosened in a future release.`