aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorDean Rasheed <dean.a.rasheed@gmail.com>2024-03-13 13:15:07 +0000
committerDean Rasheed <dean.a.rasheed@gmail.com>2024-03-13 13:15:07 +0000
commitd4c573d8e81ed28ee335e9cb2115098b99d38e71 (patch)
tree0662d405bef8fcf5ad3e1dcd417df0c809ef4430 /src/backend/executor/nodeModifyTable.c
parent9158e4b9eb9916fa586feb26a6149b59566b78e1 (diff)
downloadpostgresql-d4c573d8e81ed28ee335e9cb2115098b99d38e71.tar.gz
postgresql-d4c573d8e81ed28ee335e9cb2115098b99d38e71.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/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions