Skip to content

Commit 2791d49

Browse files
committed
Doc: include MERGE in variable substitution command list
Backpatch to 15, where MERGE was introduced. Reported-by: <emorgunov@mail.ru> Author: David Rowley <dgrowleyml@gmail.com> Discussion: https://postgr.es/m/176278494385.770.15550176063450771532@wrigleys.postgresql.org Backpatch-through: 15
1 parent 414e1ec commit 2791d49

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

doc/src/sgml/plpgsql.sgml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4913,13 +4913,13 @@ $$ LANGUAGE plpgsql;
49134913
<para>
49144914
Variable substitution currently works only in <command>SELECT</command>,
49154915
<command>INSERT</command>, <command>UPDATE</command>,
4916-
<command>DELETE</command>, and commands containing one of
4917-
these (such as <command>EXPLAIN</command> and <command>CREATE TABLE
4918-
... AS SELECT</command>),
4919-
because the main SQL engine allows query parameters only in these
4920-
commands. To use a non-constant name or value in other statement
4921-
types (generically called utility statements), you must construct
4922-
the utility statement as a string and <command>EXECUTE</command> it.
4916+
<command>DELETE</command>, <command>MERGE</command> and commands
4917+
containing one of these (such as <command>EXPLAIN</command> and
4918+
<command>CREATE TABLE ... AS SELECT</command>), because the main SQL
4919+
engine allows query parameters only in these commands. To use a
4920+
non-constant name or value in other statement types (generically called
4921+
utility statements), you must construct the utility statement as a string
4922+
and <command>EXECUTE</command> it.
49234923
</para>
49244924

49254925
</sect2>

0 commit comments

Comments
 (0)