diff options
| author | Dean Rasheed <dean.a.rasheed@gmail.com> | 2024-03-13 13:16:24 +0000 |
|---|---|---|
| committer | Dean Rasheed <dean.a.rasheed@gmail.com> | 2024-03-13 13:16:24 +0000 |
| commit | 97d4262683acb586778af2b2a3721fa7cdc402f1 (patch) | |
| tree | 72cb0ab4d38657a661ab6212e42b78b5894cb336 /src/backend/parser/parse_merge.c | |
| parent | a3da95deee38ee067b0bead639c830eacbe894d5 (diff) | |
| download | postgresql-97d4262683acb586778af2b2a3721fa7cdc402f1.tar.gz postgresql-97d4262683acb586778af2b2a3721fa7cdc402f1.zip | |
doc: Improve a couple of places in the MERGE docs.
In the synopsis, make the syntax for merge_update consistent with the
syntax for a plain UPDATE command. It was missing the optional "ROW"
keyword that can be used in a multi-column assignment, and the option
to assign from a multi-column subquery, both of which have been
supported by MERGE since it was introduced.
In the parameters section for the with_query parameter, mention that
WITH RECURSIVE isn't supported, since this is different from plain
INSERT, UPDATE, and DELETE commands. While at it, move that entry to
the top of the list, for consistency with the other pages.
Back-patch to v15, where MERGE was introduced.
Discussion: https://postgr.es/m/CAEZATCWoQyWkMFfu7JXXQr8dA6%3DgxjhYzgpuBP2oz0QoJTxGWw%40mail.gmail.com
Diffstat (limited to 'src/backend/parser/parse_merge.c')
0 files changed, 0 insertions, 0 deletions