postgres.git / summary / log / commit / refs

commit    7f5f74686dc3373626ce7e77d47b10c02cc48279
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Mon May 28 17:16:02 2018 +0000
First released in: 11.0, 9.3.24, 9.4.19, 9.5.14, 9.6.10, 10.5

    doc:  adjust DECLARE docs to mention FOR UPDATE behavior
    
    Reported-by: Peter Eisentraut
    
    Discussion: https://postgr.es/m/8dc63ba7-dc56-fc7c-fc16-4fae03e3bfe6@2ndquadrant.com
    
    Author: Peter Eisentraut, Tom Lane, me
    
    Backpatch-through: 9.3


 doc/src/sgml/ref/declare.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml
index d500faaa743..67a4cd8bae1 100644
--- a/doc/src/sgml/ref/declare.sgml
+++ b/doc/src/sgml/ref/declare.sgml
@@ -271,7 +271,8 @@ DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ INSENSITI
      and not use grouping or <literal>ORDER BY</>).  Cursors
      that are not simply updatable might work, or might not, depending on plan
      choice details; so in the worst case, an application might work in testing
-     and then fail in production.
+     and then fail in production.  If <literal>FOR UPDATE</literal> is
+     specified, the cursor is guaranteed to be updatable.
     </para>
 
     <para>


[parent: da757bf0ffb0]