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:29 -0400 |
| commit | 6af9ee4c8c8f31cbf2e76166d1d9868876f60aea (patch) | |
| tree | 72e87535046d274d3795780cc25b4bffffebf2aa /src/backend/access/common | |
| parent | 18382ae7ede9a330d997ca4d53cb429ba2c4d5fd (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/access/common')
0 files changed, 0 insertions, 0 deletions
