diff options
author | unknown <timour@askmonty.org> | 2011-09-01 23:53:12 +0300 |
---|---|---|
committer | unknown <timour@askmonty.org> | 2011-09-01 23:53:12 +0300 |
commit | ea8aa329099ee28ec6f1266d8d01a6fc664259cf (patch) | |
tree | 8b9a0b43ee89cd8fbae14deeb12012a2b7b83cdd /mysql-test/r/explain.result | |
parent | 11ebbabb087a7bd6c315e6412d8e8ee677c6217b (diff) | |
download | mariadb-git-ea8aa329099ee28ec6f1266d8d01a6fc664259cf.tar.gz |
Fix for bug lp:834492
Analysis:
In the test query semi-join merges the inner-most subquery
into the outer subquery, and the optimization of the merged
subquery finds some new index access methods. Later the
IN-EXISTS transformation is applied to the unmerged subquery.
Since the optimizer is instructed to not consider
materialization, it reoptimizes the plan in-place to take into
account the new IN-EXISTS conditions. Just before reoptimization
JOIN::choose_subquery_plan resets the query plan, which also
resets the access methods found during the semi-join merge.
Then reoptimization discovers there are no new access methods,
but it leaves the query plan in its reset state. Later semi-join
crashes because it assumes these access methods are present.
Solution:
When reoptimizing in-place, reset the query plan only after new
access methods were discovered. If no new access methods were
discovered, leave the current plan as it was.
Diffstat (limited to 'mysql-test/r/explain.result')
0 files changed, 0 insertions, 0 deletions