Skip to content

Commit 5eaee9b

Browse files
committed
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: 05d8a56 Discussion: https://www.postgresql.org/message-id/20170614.110826.425627939780392324.t-ishii%40sraoss.co.jp
1 parent fc267a0 commit 5eaee9b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/src/sgml/high-availability.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1608,7 +1608,7 @@ if (!triggered)
16081608

16091609
<para>
16101610
In normal operation, <quote>read-only</> transactions are allowed to
1611-
update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and
1611+
use <command>LISTEN</>, <command>UNLISTEN</>, and
16121612
<command>NOTIFY</>, so Hot Standby sessions operate under slightly tighter
16131613
restrictions than ordinary read-only sessions. It is possible that some
16141614
of these restrictions might be loosened in a future release.

0 commit comments

Comments
 (0)