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 | 06663971bba43ea967daf00fff0b70ee066c3a13 (patch) | |
tree | b6687f146b3cf5746bbd3366b37ed6738c202a03 /src/backend/access/gist | |
parent | 34a4318e7d64d93d48add738257ae0f6289799f6 (diff) | |
download | postgresql-06663971bba43ea967daf00fff0b70ee066c3a13.tar.gz postgresql-06663971bba43ea967daf00fff0b70ee066c3a13.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')
0 files changed, 0 insertions, 0 deletions