postgres.git / summary / log / commit / refs

commit    e3f87aae9316d42ece1912d1cae34ec0ba8142c8
Author:   Tatsuo Ishii <ishii@postgresql.org>
Date:     Thu Jun 15 01:01:39 2017 +0000

    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 a1960299c00..774d2b4bce6 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1783,7 +1783,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: 318fd99ce7e7]