EXPLAIN statement can be used
to obtain information about how MySQL executes a statement:
EXPLAIN is used with an
explainable statement, MySQL displays information from the
optimizer about the statement execution plan. That is, MySQL
explains how it would process the statement, including
information about how tables are joined and in which order.
For information about using
EXPLAIN to obtain execution
plan information, see Section 8.8.2, “
EXPLAIN Output Format”.
EXPLAIN is used with
than an explainable statement, it displays the execution
plan for the statement executing in the named connection.
See Section 8.8.3, “Obtaining Execution Plan Information for a Named Connection”.
Before MySQL 5.7.3,
EXTENDED can be used to obtain additional
execution plan information. See
Section 8.8.4, “
EXPLAIN EXTENDED Output Format”. As of MySQL 5.7.3,
extended output is enabled by default and the
EXTENDED keyword is unnecessry.
Before MySQL 5.7.3,
PARTITIONS is useful for examining queries
involving partitioned tables. See
Section 17.3.5, “Obtaining Information About Partitions”. As of MySQL 5.7.3,
partition information is enabled by default and the
PARTITIONS keyword is unnecessry.
FORMAT option can be used to select
the output format.
the output in tabular format. This is the default if no
FORMAT option is present.
JSON format displays the information in
JSON format. With
FORMAT = JSON, the
output includes extended and partition information.
With the help of
EXPLAIN, you can
see where you should add indexes to tables so that the statement
executes faster by using indexes to find rows. You can also use
EXPLAIN to check whether the
optimizer joins the tables in an optimal order. To give a hint
to the optimizer to use a join order corresponding to the order
in which the tables are named in a
SELECT statement, begin the
SELECT STRAIGHT_JOIN rather
Section 13.2.9, “
The optimizer trace may sometimes provide information
complementary to that of
However, the optimizer trace format and content are subject to
change between versions. For details, see
Internals: Tracing the Optimizer.
If you have a problem with indexes not being used when you
believe that they should be, run
TABLE to update table statistics, such as cardinality
of keys, that can affect the choices the optimizer makes. See
Section 220.127.116.11, “
ANALYZE TABLE Syntax”.