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 | 4d94b5f1f003404f86b2659eff9814466d03640e (patch) | |
tree | 8fd531f64ad1bc662b642249dbcae8630da8eb6c /src/backend/access/gist/gistxlog.c | |
parent | aa9f8cb131a91df16db69fd271f81e761db29625 (diff) | |
download | postgresql-4d94b5f1f003404f86b2659eff9814466d03640e.tar.gz postgresql-4d94b5f1f003404f86b2659eff9814466d03640e.zip |
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/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions