]> granicus.if.org Git - postgresql/commitdiff
doc: adjust DECLARE docs to mention FOR UPDATE behavior
authorBruce Momjian <bruce@momjian.us>
Mon, 28 May 2018 17:16:02 +0000 (13:16 -0400)
committerBruce Momjian <bruce@momjian.us>
Mon, 28 May 2018 17:16:02 +0000 (13:16 -0400)
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

index 5cb85cc568fc6fe0a2d7809e32623f690959d1cc..864c3d75f7f8e62150bb0916fc48ccc378c0e8d0 100644 (file)
@@ -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>