aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTatsuo Ishii <ishii@postgresql.org>2017-06-15 10:01:39 +0900
committerTatsuo Ishii <ishii@postgresql.org>2017-06-15 10:01:39 +0900
commit6108348c09df33773bed6e0ac762fe47bdcbb9e6 (patch)
treedb2b54ba72ba71efb35a30880079eab340eb429c
parentf32d57fd7088a558dadbe21b9859b09d2f877c19 (diff)
downloadpostgresql-6108348c09df33773bed6e0ac762fe47bdcbb9e6.tar.gz
postgresql-6108348c09df33773bed6e0ac762fe47bdcbb9e6.zip
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
-rw-r--r--doc/src/sgml/high-availability.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index ce67d4a5e3b..72eb073621f 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.