debugging how query plans are made

Zardosht Kasheff <[email protected]> Tue, 12 Feb 2013 08:54:55 -0500
Newsgroups gmane.comp.db.mysql.devel
Message-ID <CABFd+SFF2MmLRKapVrraeTfdZsgrEzRtuBgtd_e_nN4C9R98-w@mail.gmail.com>
Hello all,

In MySQL and/or MariaDB, are there any hooks or methods one can use to
learn why a query plan is chosen over alternatives? We sometimes
notice that a different query plan is chosen for us than InnoDB (which
may be fine, given we are a different storage engine), and we would
like to better understand why. Is there any debug parameter that gets
MySQL to output decisions made in the optimizer?

Thanks
-Zardosht

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    http://lists.mysql.com/internals