diff options
author | Tatsuo Ishii <ishii@postgresql.org> | 2017-06-15 10:01:39 +0900 |
---|---|---|
committer | Tatsuo Ishii <ishii@postgresql.org> | 2017-06-15 10:08:53 +0900 |
commit | 5eaee9b4c4af3c3cc7f52f921e03512699dcd887 (patch) | |
tree | 06915334b6db4f8364934e6befb21aa095a09047 | |
parent | fc267a0c3c652996cb7f49967d5bd11522a32166 (diff) |
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.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index c01f83a9460..2d5d23526b8 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1608,7 +1608,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. |