[MDEV-7923] forcing index changes query plan (even if default chose that index) Created: 2015-04-06 Updated: 2015-06-16 Resolved: 2015-06-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 5.5.42 |
| Fix Version/s: | 5.5.44, 10.0.20 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Daniel Black | Assignee: | Sergei Petrunia |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Noticed in using ftp://ftp.askmonty.org/public/mdev7786.dump.gz test case:
Even though idx2 was chosen for t2 already, forcing it changed the query plan (in this case for the better but hopefully the Does method of use on the index need to be specified in the force index? |
| Comments |
| Comment by Sergei Petrunia [ 2015-06-10 ] |
|
Fixed by the fix for |
| Comment by Daniel Black [ 2015-06-11 ] |
|
There is no forcing of any index in the test case for this bug I also can't see any indication of code path changes that corrected the change in query plan based on forcing an index. https://github.com/MariaDB/server/commit/992d782d784fb960a705a3532562224d16c6a6d0 |
| Comment by Sergei Golubchik [ 2015-06-16 ] |
|
I've asked that on IRC, the answer was
|