postgres.git / summary / log / commit / refs

commit    7efc08dec9c737e92388fe2665f2bc1d4e3c1970
Author:   Tatsuo Ishii <ishii@postgresql.org>
Date:     Thu Jun 15 01:01:39 2017 +0000
First released in: 10.0, 9.2.22, 9.3.18, 9.4.13, 9.5.8, 9.6.4

    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


 doc/src/sgml/high-availability.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index ebefe0f6b1c..4a44271484b 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1730,7 +1730,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.


[parent: df6896c12e98]