diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-08-05 14:39:07 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-08-05 14:39:07 -0400 |
commit | 08dee567ed6b168e5646718da0279c46ede77ffc (patch) | |
tree | e12371a35750bb0025df31528f470fb8df0f60a1 /src/backend/regex/regc_cvec.c | |
parent | 4eb4e71119780a15168d03c933f41bc04b1ecd4e (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/regex/regc_cvec.c')
0 files changed, 0 insertions, 0 deletions