diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-05-02 15:56:36 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-05-02 15:57:28 -0400 |
commit | dcc685debb02c507b88aa8052f9e6334a7c3f830 (patch) | |
tree | c8db1d89f77c7e3b020fa4777d57702834647915 /src/backend/regex/regexec.c | |
parent | 52897e54db1000f2fa45b31e02eb252dd0573516 (diff) | |
download | postgresql-dcc685debb02c507b88aa8052f9e6334a7c3f830.tar.gz postgresql-dcc685debb02c507b88aa8052f9e6334a7c3f830.zip |
Fix pull_up_sublinks' failure to handle nested pull-up opportunities.
After finding an EXISTS or ANY sub-select that can be converted to a
semi-join or anti-join, we should recurse into the body of the sub-select.
This allows cases such as EXISTS-within-EXISTS to be optimized properly.
The original coding would leave the lower sub-select as a SubLink, which
is no better and often worse than what we can do with a join. Per example
from Wayne Conrad.
Back-patch to 8.4. There is a related issue in older versions' handling
of pull_up_IN_clauses, but they're lame enough anyway about the whole area
that it seems not worth the extra work to try to fix.
Diffstat (limited to 'src/backend/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions