Non optimal index choice, depending on index creation order

Bug #639949 reported by jocelyn fournier
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nominated for 5.1 by jocelyn fournier
Nominated for 5.2 by jocelyn fournier
Nominated for 5.3 by jocelyn fournier

Bug Description


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 :

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,
  Jocelyn Fournier

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers