Bug #33486 Optimizer trace tool needed
| Submitted: | 22 Dec 2007 21:04 | Modified: | 8 Dec 2011 3:35 |
|---|---|---|---|
| Reporter: | Mark Callaghan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S4 (Feature request) |
| Version: | 5.0 | OS: | Any |
| Assigned to: | Guilhem Bichot | CPU Architecture: | Any |
| Tags: | debug, Optimizer, trace | ||
[22 Dec 2007 21:04]
Mark Callaghan
[24 Dec 2007 14:59]
Valeriy Kravchuk
Thank you for a reasonable feature request.
[21 Nov 2011 15:30]
Guilhem Bichot
This has been implemented in 5.6.3. Not all decisions are traced yet, but quite a few are. Doc: http://forge.mysql.com/wiki/MySQL_Internals_Optimizer_tracing and also http://jorgenloland.blogspot.com/2011/10/optimizer-tracing-query-execution-plan.html http://guilhembichot.blogspot.com/2011/09/optimizer-tracing-how-to-configure-it.html
[8 Dec 2011 3:35]
Mark Callaghan
Wow, nice work
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.