aboutsummaryrefslogtreecommitdiff
path: root/src/backend/regex/regerror.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
commit48d4f1e39df53ef3ab44fde2ff84ea778f672a9f (patch)
tree9b002e2a57d74dd489387af15fd22b139bb9af21 /src/backend/regex/regerror.c
parentdacbdda1092e20507249bade076c859993f5e837 (diff)
downloadpostgresql-48d4f1e39df53ef3ab44fde2ff84ea778f672a9f.tar.gz
postgresql-48d4f1e39df53ef3ab44fde2ff84ea778f672a9f.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/regex/regerror.c')
0 files changed, 0 insertions, 0 deletions