[MDEV-626] LP:639949 - Non optimal index choice, depending on index creation order Created: 2010-09-15 Updated: 2014-10-11 Resolved: 2012-10-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | jocelyn fournier | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Launchpad, order-by-optimization | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Hi, There are several simple cases where MySQL optimiser doesn't select the right index. This entails strong performance issues, and force the developers to hack their applications, using USE INDEX (when it's possible...) This wrong optimizer behaviour is explained in detail here : http://bugs.mysql.com/bug.php?id=36817 The bugs also occurs both in MariaDB 5.1 & 5.2. Since this bug is around for more than 2 years now, I really hope it could be fixed really soon in MariaDB. Thanks and regards, |
| Comments |
| Comment by Rasmus Johansson (Inactive) [ 2010-11-23 ] |
|
Launchpad bug id: 639949 |