aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeAppend.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-12-11 15:52:16 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2015-12-11 15:52:39 -0500
commitdc4518814ecc2ae319c4d1679ee079e47dbd78e9 (patch)
tree5158f9a835583bc58b7f715784608c5d4b48cdf3 /src/backend/executor/nodeAppend.c
parent12a54c888cf7bd9c37c4ce420e84cb52debe0184 (diff)
downloadpostgresql-dc4518814ecc2ae319c4d1679ee079e47dbd78e9.tar.gz
postgresql-dc4518814ecc2ae319c4d1679ee079e47dbd78e9.zip
Get rid of the planner's LateralJoinInfo data structure.
I originally modeled this data structure on SpecialJoinInfo, but after commit acfcd45cacb6df23 that looks like a pretty poor decision. All we really need is relid sets identifying laterally-referenced rels; and most of the time, what we want to know about includes indirect lateral references, a case the LateralJoinInfo data was unsuited to compute with any efficiency. The previous commit redefined RelOptInfo.lateral_relids as the transitive closure of lateral references, so that it easily supports checking indirect references. For the places where we really do want just direct references, add a new RelOptInfo field direct_lateral_relids, which is easily set up as a copy of lateral_relids before we perform the transitive closure calculation. Then we can just drop lateral_info_list and LateralJoinInfo and the supporting code. This makes the planner's handling of lateral references noticeably more efficient, and shorter too. Such a change can't be back-patched into stable branches for fear of breaking extensions that might be looking at the planner's data structures; but it seems not too late to push it into 9.5, so I've done so.
Diffstat (limited to 'src/backend/executor/nodeAppend.c')
0 files changed, 0 insertions, 0 deletions