database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-19 17:02:53 +03:00
Code Activity

Update some comments that should've covered MERGE

Browse Source 
Oversight in 7103ebb7aa.  Backpatch to 15.

Author: Richard Guo <guofenglinux@gmail.com>
Discussion: https://postgr.es/m/CAMbWs48gnDjZXq3-b56dVpQCNUJ5hD9kdtWN4QFwKCEapspNsA@mail.gmail.com
This commit is contained in:
Alvaro Herrera
2022-10-24 12:52:43 +02:00
parent 8328a15f8f
commit 3b2db22fe2
14 changed files with 42 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/include/nodes/pathnodes.h
View File

@@ -328,11 +328,11 @@ struct PlannerInfo
/*
* all_result_relids is empty for SELECT, otherwise it contains at least
* parse->resultRelation. For UPDATE/DELETE across an inheritance or
* partitioning tree, the result rel's child relids are added. When using
* multi-level partitioning, intermediate partitioned rels are included.
* leaf_result_relids is similar except that only actual result tables,
* not partitioned tables, are included in it.
* parse->resultRelation. For UPDATE/DELETE/MERGE across an inheritance
* or partitioning tree, the result rel's child relids are added. When
* using multi-level partitioning, intermediate partitioned rels are
* included. leaf_result_relids is similar except that only actual result
* tables, not partitioned tables, are included in it.
*/
/* set of all result relids */
Relids all_result_relids;
@@ -2792,10 +2792,10 @@ typedef struct AppendRelInfo
} AppendRelInfo;
/*
* Information about a row-identity "resjunk" column in UPDATE/DELETE.
* Information about a row-identity "resjunk" column in UPDATE/DELETE/MERGE.
*
* In partitioned UPDATE/DELETE it's important for child partitions to share
* row-identity columns whenever possible, so as not to chew up too many
* In partitioned UPDATE/DELETE/MERGE it's important for child partitions to
* share row-identity columns whenever possible, so as not to chew up too many
* targetlist columns. We use these structs to track which identity columns
* have been requested. In the finished plan, each of these will give rise
* to one resjunk entry in the targetlist of the ModifyTable's subplan node.