diff options
author | Tom Lane | 2012-08-19 18:12:16 +0000 |
---|---|---|
committer | Tom Lane | 2012-08-19 18:12:16 +0000 |
commit | 092d7ded29f36b0539046b23b81b9f0bf2d637f1 (patch) | |
tree | 9d42dc496cf768b95fafd903f01bb9ee9dbd9b73 /src/backend/optimizer | |
parent | c246eb5aafe66d5537b468d6da2116c462775faf (diff) |
Allow OLD and NEW in multi-row VALUES within rules.
Now that we have LATERAL, it's fairly painless to allow this case, which
was left as a TODO in the original multi-row VALUES implementation.
Diffstat (limited to 'src/backend/optimizer')
-rw-r--r-- | src/backend/optimizer/path/allpaths.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/src/backend/optimizer/path/allpaths.c b/src/backend/optimizer/path/allpaths.c index dfb0b38448b..23a8afb3d0c 100644 --- a/src/backend/optimizer/path/allpaths.c +++ b/src/backend/optimizer/path/allpaths.c @@ -1221,9 +1221,7 @@ set_values_pathlist(PlannerInfo *root, RelOptInfo *rel, RangeTblEntry *rte) /* * If it's a LATERAL RTE, it might contain some Vars of the current query - * level, requiring it to be treated as parameterized. (NB: even though - * the parser never marks VALUES RTEs as LATERAL, they could be so marked - * by now, as a result of subquery pullup.) + * level, requiring it to be treated as parameterized. */ if (rte->lateral) { |