diff options
| author | Bruce Momjian | 2018-05-28 17:16:02 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2018-05-28 17:16:02 +0000 |
| commit | 99164e6952917009929026a9a11e4a500f599c40 (patch) | |
| tree | 633525a52d98e1e766ba90f8b86bfd8c0dd1c619 | |
| parent | f963f80970641246cbba172e197068193ad65189 (diff) | |
doc: adjust DECLARE docs to mention FOR UPDATE behavior
Reported-by: Peter Eisentraut
Discussion: https://postgr.es/m/[email protected]
Author: Peter Eisentraut, Tom Lane, me
Backpatch-through: 9.3
| -rw-r--r-- | doc/src/sgml/ref/declare.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml index 648c2950f41..34ca9df2437 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</literal>). 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> |