summaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeLimit.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-08-05 14:39:07 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-08-05 14:39:07 -0400
commit9bc4d5927c573d5fa5081b37feab06f07b7b5b2c (patch)
treec5b42af23b2a841530aa84eb5086f9bfa78a6822 /src/backend/executor/nodeLimit.c
parentea1703eb490b34ec689c7b1d32c06634871ada36 (diff)
Make real sure we don't reassociate joins into or out of SEMI/ANTI joins.
Per the discussion in optimizer/README, it's unsafe to reassociate anything into or out of the RHS of a SEMI or ANTI join. An example from Piotr Stefaniak showed that join_is_legal() wasn't sufficiently enforcing this rule, so lock it down a little harder. I couldn't find a reasonably simple example of the optimizer trying to do this, so no new regression test. (Piotr's example involved the random search in GEQO accidentally trying an invalid case and triggering a sanity check way downstream in clause selectivity estimation, which did not seem like a sequence of events that would be useful to memorialize in a regression test as-is.) Back-patch to all active branches.
Diffstat (limited to 'src/backend/executor/nodeLimit.c')
0 files changed, 0 insertions, 0 deletions