Mysql 的 explain 详解

explain 基本作用
1、explain 作用和 describe 一致；
2、explian tbl_name 的作用同 show columns from tbl_name 是一致的；
3、如果在 select 语句之前加入该关键字，则可以模拟优化器执行 sql，从而得知 Mysql 如何处理这条 sql 语句的，帮助我们分析查询语句提高性能；

mysql> explain `order`;
+---------+-------------+------+-----+---------+----------------+
| Field   | Type        | Null | Key | Default | Extra          |
+---------+-------------+------+-----+---------+----------------+
| id      | int(11)     | NO   | PRI | NULL    | auto_increment |
| orderNo | varchar(45) | YES  | UNI | NULL    |                |
| price   | int(11)     | YES  |     | NULL    |                |
| status  | tinyint(4)  | YES  |     | NULL    |                |
| date    | datetime    | YES  |     | NULL    |                |
| method  | tinyint(4)  | YES  |     | NULL    |                |
+---------+-------------+------+-----+---------+----------------+
6 rows in set (0.00 sec)

mysql> describe `order`;
+---------+-------------+------+-----+---------+----------------+
| Field   | Type        | Null | Key | Default | Extra          |
+---------+-------------+------+-----+---------+----------------+
| id      | int(11)     | NO   | PRI | NULL    | auto_increment |
| orderNo | varchar(45) | YES  | UNI | NULL    |                |
| price   | int(11)     | YES  |     | NULL    |                |
| status  | tinyint(4)  | YES  |     | NULL    |                |
| date    | datetime    | YES  |     | NULL    |                |
| method  | tinyint(4)  | YES  |     | NULL    |                |
+---------+-------------+------+-----+---------+----------------+

explain 分析 select 语句结果

mysql> explain select * from `order`;
+----+-------------+-------+------------+------+---------------+------+---------+------+---------+----------+-------+
| id | select_type | table | partitions | type | possible_keys | key  | key_len | ref  | rows    | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+------+---------+----------+-------+
|  1 | SIMPLE      | order | NULL       | ALL  | NULL          | NULL | NULL    | NULL | 4854583 |   100.00 | NULL  |
+----+-------------+-------+------------+------+---------------+------+---------+------+---------+----------+-------+

explain 结果分析

  • 1、id

id 是一组数字，表示查询过程中操作表的顺序，共分为三种情况：
1）id 相同，执行顺序自上而下；

mysql> explain select t1.*
    -> from orders t1, order_detail t2, seller t3
    -> where t1.orderNo = t2.orderNo and t2.sellerId = t3.sellerId;
+----+-------------+-------+------------+------+---------------+------+---------+------+---------+----------+----------------------------------------------------+
| id | select_type | table | partitions | type | possible_keys | key  | key_len | ref  | rows    | filtered | Extra                                              |
+----+-------------+-------+------------+------+---------------+------+---------+------+---------+----------+----------------------------------------------------+
|  1 | SIMPLE      | t3    | NULL       | ALL  | NULL          | NULL | NULL    | NULL |       3 |   100.00 | NULL                                               |
|  1 | SIMPLE      | t2    | NULL       | ALL  | NULL          | NULL | NULL    | NULL |       5 |    20.00 | Using where; Using join buffer (Block Nested Loop) |
|  1 | SIMPLE      | t1    | NULL       | ALL  | NULL          | NULL | NULL    | NULL | 4854583 |   100.00 | Using where; Using join buffer (Block Nested Loop) |
+----+-------------+-------+------------+------+---------------+------+---------+------+---------+----------+----------------------------------------------------+
3 rows in set, 1 warning (0.02 sec)

2）id 不同，如果是子查询，id的序号会递增，id值越大优先级越高，越先被执行；

mysql> explain select * from orders where orderNo = ( select orderNo from order_detail where sellerId = (select sellerId from seller where id = 1));
+----+-------------+--------------+------------+-------+---------------+---------+---------+-------+---------+----------+-------------+
| id | select_type | table        | partitions | type  | possible_keys | key     | key_len | ref   | rows    | filtered | Extra       |
+----+-------------+--------------+------------+-------+---------------+---------+---------+-------+---------+----------+-------------+
|  1 | PRIMARY     | orders       | NULL       | ALL   | NULL          | NULL    | NULL    | NULL  | 4854583 |   100.00 | Using where |
|  2 | SUBQUERY    | order_detail | NULL       | ALL   | NULL          | NULL    | NULL    | NULL  |       5 |    20.00 | Using where |
|  3 | SUBQUERY    | seller       | NULL       | const | PRIMARY       | PRIMARY | 4       | const |       1 |   100.00 | NULL        |
+----+-------------+--------------+------------+-------+---------------+---------+---------+-------+---------+----------+-------------+
3 rows in set, 1 warning (0.01 sec)

3）id相同不同，同时存在。id 相同的认为一组自上而下顺序执行，id 不同，id 值越大越先执行；

mysql> explain select t1.* from (
    -> select orderNo
    -> from order_detail
    -> where id = 1) t2, orders t1
    -> where t1.orderNo = t2.orderNo;
+----+-------------+--------------+--------+---------------+---------+---------+------+------+-------------+
| id | select_type | table        | type   | possible_keys | key     | key_len | ref  | rows | Extra       |
+----+-------------+--------------+--------+---------------+---------+---------+------+------+-------------+
|  1 | PRIMARY     | <derived2>   | system | NULL          | NULL    | NULL    | NULL |    1 |             |
|  1 | PRIMARY     | t1           | ALL    | NULL          | NULL    | NULL    | NULL |   50 | Using where |
|  2 | DERIVED     | order_detail | const  | PRIMARY       | PRIMARY | 4       |      |    1 |             |
+----+-------------+--------------+--------+---------------+---------+---------+------+------+-------------+
3 rows in set (0.00 sec)
  • 2、select_type

1） simple 简单 sql 查询，不包含子查询或者 union

mysql> explain select * from orders;
+----+-------------+--------+------+---------------+------+---------+------+------+-------+
| id | select_type | table  | type | possible_keys | key  | key_len | ref  | rows | Extra |
+----+-------------+--------+------+---------------+------+---------+------+------+-------+
|  1 | SIMPLE      | orders | ALL  | NULL          | NULL | NULL    | NULL |   50 |       |
+----+-------------+--------+------+---------------+------+---------+------+------+-------+
1 row in set (0.00 sec)

2）primary 查询过程中包含其他子部分

mysql> explain select * from (select orderNo from order_detail where id = 1) t;
+----+-------------+--------------+--------+---------------+---------+---------+------+------+-------+
| id | select_type | table        | type   | possible_keys | key     | key_len | ref  | rows | Extra |
+----+-------------+--------------+--------+---------------+---------+---------+------+------+-------+
|  1 | PRIMARY     | <derived2>   | system | NULL          | NULL    | NULL    | NULL |    1 |       |
|  2 | DERIVED     | order_detail | const  | PRIMARY       | PRIMARY | 4       |      |    1 |       |
+----+-------------+--------------+--------+---------------+---------+---------+------+------+-------+
2 rows in set (0.00 sec)

3） subquery 子查询的第一个 select

mysql> explain select * from orders where orderNo = (select orderNo from order_detail where id = 1);
+----+-------------+--------------+-------+---------------+---------+---------+-------+------+-------------+
| id | select_type | table        | type  | possible_keys | key     | key_len | ref   | rows | Extra       |
+----+-------------+--------------+-------+---------------+---------+---------+-------+------+-------------+
|  1 | PRIMARY     | orders       | ALL   | NULL          | NULL    | NULL    | NULL  |   50 | Using where |
|  2 | SUBQUERY    | order_detail | const | PRIMARY       | PRIMARY | 4       | const |    1 |             |
+----+-------------+--------------+-------+---------------+---------+---------+-------+------+-------------+
2 rows in set (0.01 sec)

4）union union中的从第二个之后的 select；union result union的结果

mysql> explain select * from orders where id = 1
    -> union
    -> select * from orders where id = 2;
+----+--------------+------------+-------+---------------+---------+---------+-------+------+-------+
| id | select_type  | table      | type  | possible_keys | key     | key_len | ref   | rows | Extra |
+----+--------------+------------+-------+---------------+---------+---------+-------+------+-------+
|  1 | PRIMARY      | orders     | const | PRIMARY       | PRIMARY | 4       | const |    1 |       |
|  2 | UNION        | orders     | const | PRIMARY       | PRIMARY | 4       | const |    1 |       |
| NULL | UNION RESULT | <union1,2> | ALL   | NULL          | NULL    | NULL    | NULL  | NULL |       |
+----+--------------+------------+-------+---------------+---------+---------+-------+------+-------+
3 rows in set (0.00 sec)

5）derived（衍生） 在 from 包含的子查询，MySQL会递归执行这些子查询，把结果放在临时表里；（3中有derived）

  • 3、table

查询结果数据引用的表

  • 4、type

1）system 表只有一行记录（等于系统表），平时很少出现，时 const 的一个特例；

2）const 表中最多只有一行匹配行，用于查询条件中的列是 primary key 或者 unique 索引的列；

mysql> show index from orders;
+--------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| Table  | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment |
+--------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| orders |          0 | PRIMARY  |            1 | id          | A         |          50 |     NULL | NULL   |      | BTREE      |         |               |
| orders |          0 | un_index |            1 | orderNo     | A         |          50 |     NULL | NULL   | YES  | BTREE      |         |               |
+--------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
2 rows in set (0.00 sec)

mysql> explain select * from orders where orderNo = 'dac4c327-9810-11eb-af55-000c296fcfe0';
+----+-------------+--------+-------+---------------+----------+---------+-------+------+-------+
| id | select_type | table  | type  | possible_keys | key      | key_len | ref   | rows | Extra |
+----+-------------+--------+-------+---------------+----------+---------+-------+------+-------+
|  1 | SIMPLE      | orders | const | un_index      | un_index | 48      | const |    1 |       |
+----+-------------+--------+-------+---------------+----------+---------+-------+------+-------+
1 row in set (0.00 sec)

3）eq_ref 唯一性索引，对于每个索引键，表中只有一条记录与之匹配，常见于主键或唯一索引扫描;

mysql> explain select * from orders t1, order_detail t2 where t1.id = t2.id;
+----+-------------+-------+--------+---------------+---------+---------+------------+------+-------+
| id | select_type | table | type   | possible_keys | key     | key_len | ref        | rows | Extra |
+----+-------------+-------+--------+---------------+---------+---------+------------+------+-------+
|  1 | SIMPLE      | t2    | ALL    | PRIMARY       | NULL    | NULL    | NULL       |    4 |       |
|  1 | SIMPLE      | t1    | eq_ref | PRIMARY       | PRIMARY | 4       | test.t2.id |    1 |       |
+----+-------------+-------+--------+---------------+---------+---------+------------+------+-------+
2 rows in set (0.00 sec)

4）ref 非唯一索引，返回匹配结果的所有行；

mysql> create index in_or on orders(orderNo);
Query OK, 0 rows affected (0.45 sec)
Records: 0  Duplicates: 0  Warnings: 0

mysql> explain select * from orders where orderNo = 'dac4c327-9810-11eb-af55-000c296fcfe0';
+----+-------------+--------+------+---------------+-------+---------+-------+------+-------------+
| id | select_type | table  | type | possible_keys | key   | key_len | ref   | rows | Extra       |
+----+-------------+--------+------+---------------+-------+---------+-------+------+-------------+
|  1 | SIMPLE      | orders | ref  | in_or         | in_or | 48      | const |    1 | Using where |
+----+-------------+--------+------+---------------+-------+---------+-------+------+-------------+
1 row in set (0.05 sec)

5）range 只检索给定范围的行，使用一个索引来选择行。key列显示使用了哪个索引
一般就是在你的where语句中出现了between、<、>、in等的查询
这种范围扫描索引扫描比全表扫描要好，因为他只需要开始索引的某一点，而结束语另一点，不用扫描全部索引

mysql> explain select * from orders where id > 34;
+----+-------------+--------+-------+---------------+---------+---------+------+------+-------------+
| id | select_type | table  | type  | possible_keys | key     | key_len | ref  | rows | Extra       |
+----+-------------+--------+-------+---------------+---------+---------+------+------+-------------+
|  1 | SIMPLE      | orders | range | PRIMARY       | PRIMARY | 4       | NULL |    4 | Using where |
+----+-------------+--------+-------+---------------+---------+---------+------+------+-------------+
1 row in set (0.00 sec)

6）index 从索引文件中读取数据，因为索引文件一般情况下比数据文件要下因此，速度更快；

mysql> explain select orderNo from orders;
+----+-------------+--------+-------+---------------+-------+---------+------+------+-------------+
| id | select_type | table  | type  | possible_keys | key   | key_len | ref  | rows | Extra       |
+----+-------------+--------+-------+---------------+-------+---------+------+------+-------------+
|  1 | SIMPLE      | orders | index | NULL          | un_or | 48      | NULL |    4 | Using index |
+----+-------------+--------+-------+---------------+-------+---------+------+------+-------------+
1 row in set (0.03 sec)

7）all 遍历全表

mysql> explain select * from orders;
+----+-------------+--------+------+---------------+------+---------+------+------+-------+
| id | select_type | table  | type | possible_keys | key  | key_len | ref  | rows | Extra |
+----+-------------+--------+------+---------------+------+---------+------+------+-------+
|  1 | SIMPLE      | orders | ALL  | NULL          | NULL | NULL    | NULL |    4 |       |
+----+-------------+--------+------+---------------+------+---------+------+------+-------+
1 row in set (0.00 sec)
  • 5、possible_keys

查询语句涉及的字段上若存在索引，则会被列出，但不一定在查询时使用到，如果为 null 则表示没有用到索引；

mysql> explain select * from orders where orderNo = 'dac4c327-9810-11eb-af55-000c296fcfe0' and id =51;
+----+-------------+--------+-------+------------------+---------+---------+-------+------+-------+
| id | select_type | table  | type  | possible_keys    | key     | key_len | ref   | rows | Extra |
+----+-------------+--------+-------+------------------+---------+---------+-------+------+-------+
|  1 | SIMPLE      | orders | const | PRIMARY,un_index | PRIMARY | 4       | const |    1 |       |
+----+-------------+--------+-------+------------------+---------+---------+-------+------+-------+
1 row in set (0.00 sec)
  • 6、key

查询过程中实际用到的索引，为 null 时表示没有用到索引；

  • 7、key_len

表示索引的字节数，key_len 显示的长度表示索引的最大长度，并不是实际使用长度，在不损失精度的情况下，长度越小越好；

  • 8、ref

显示索引那一列被使用了，如果可能的话，是一个常数。那些列或常量被用于查找索引列上的值

  • 9、rows

大致估算执行查询语句找到结果所需要读取的行数

  • 10、extra

重要的额外信息
1） Using filesort 表示 mysql 会用外部的一个索引排序，而不是按照表内的索引顺序进行读取；

mysql> explain select * from orders order by orderNo;
+----+-------------+--------+------+---------------+------+---------+------+------+----------------+
| id | select_type | table  | type | possible_keys | key  | key_len | ref  | rows | Extra          |
+----+-------------+--------+------+---------------+------+---------+------+------+----------------+
|  1 | SIMPLE      | orders | ALL  | NULL          | NULL | NULL    | NULL |    4 | Using filesort |
+----+-------------+--------+------+---------------+------+---------+------+------+----------------+
1 row in set (0.00 sec)

2） Using temporary 使用临时表存储中加数据，常用于 order by 和 group by；

mysql> explain select * from orders group by orderNo order by id desc;
+----+-------------+--------+-------+---------------+---------+---------+------+------+-----------------+
| id | select_type | table  | type  | possible_keys | key     | key_len | ref  | rows | Extra           |
+----+-------------+--------+-------+---------------+---------+---------+------+------+-----------------+
|  1 | SIMPLE      | orders | index | NULL          | PRIMARY | 4       | NULL |    4 | Using temporary |
+----+-------------+--------+-------+---------------+---------+---------+------+------+-----------------+
1 row in set (0.00 sec)
  1. Using index 使用覆盖索引
mysql> explain select orderNo from orders;
+----+-------------+--------+-------+---------------+-------+---------+------+------+-------------+
| id | select_type | table  | type  | possible_keys | key   | key_len | ref  | rows | Extra       |
+----+-------------+--------+-------+---------------+-------+---------+------+------+-------------+
|  1 | SIMPLE      | orders | index | NULL          | un_or | 48      | NULL |    4 | Using index |
+----+-------------+--------+-------+---------------+-------+---------+------+------+-------------+
1 row in set (0.00 sec)
©著作权归作者所有,转载或内容合作请联系作者
  • 人面猴
    序言：七十年代末，一起剥皮案震惊了整个滨河市，随后出现的几起案子，更是在滨河造成了极大的恐慌，老刑警刘岩，带你破解...
    沈念sama阅读 157,012评论 4赞 359
  • 死咒
    序言：滨河连续发生了三起死亡事件，死亡现场离奇诡异，居然都是意外死亡，警方通过查阅死者的电脑和手机，发现死者居然都...
    沈念sama阅读 66,589评论 1赞 290
  • 救了他两次的神仙让他今天三更去死
    文/潘晓璐 我一进店门，熙熙楼的掌柜王于贵愁眉苦脸地迎上来，“玉大人，你说我怎么就摊上这事。” “怎么了？”我有些...
    开封第一讲书人阅读 106,819评论 0赞 237
  • 道士缉凶录：失踪的卖姜人
    文/不坏的土叔 我叫张陵，是天一观的道长。 经常有香客问我，道长，这世上最难降的妖魔是什么？ 我笑而不...
    开封第一讲书人阅读 43,652评论 0赞 202
  • 港岛之恋（遗憾婚礼）
    正文 为了忘掉前任，我火速办了婚礼，结果婚礼上，老公的妹妹穿的比我还像新娘。我一直安慰自己，他们只是感情好，可当我...
    茶点故事阅读 51,954评论 3赞 285
  • 恶毒庶女顶嫁案：这布局不是一般人想出来的
    文/花漫 我一把揭开白布。 她就那样静静地躺着，像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上，一...
    开封第一讲书人阅读 40,381评论 1赞 210
  • 城市分裂传说
    那天，我揣着相机与录音，去河边找鬼。 笑死，一个胖子当着我的面吹牛，可吹牛的内容都是我干的。 我是一名探鬼主播，决...
    沈念sama阅读 31,687评论 2赞 310
  • 双鸳鸯连环套：你想象不到人心有多黑
    文/苍兰香墨 我猛地睁开眼，长吁一口气：“原来是场噩梦啊……” “哼！你这毒妇竟也来了？” 一声冷哼从身侧响起，我...
    开封第一讲书人阅读 30,404评论 0赞 194
  • 万荣杀人案实录
    序言：老挝万荣一对情侣失踪，失踪者是张志新（化名）和其女友刘颖，没想到半个月后，有当地人在树林里发现了一具尸体，经...
    沈念sama阅读 34,082评论 1赞 238
  • 护林员之死
    正文 独居荒郊野岭守林人离奇死亡，尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 30,355评论 2赞 241
  • 白月光启示录
    正文 我和宋清朗相恋三年，在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 31,880评论 1赞 255
  • 活死人
    序言：一个原本活蹦乱跳的男人离奇死亡，死状恐怖，灵堂内的尸体忽然破棺而出，到底是诈尸还是另有隐情，我是刑警宁泽，带...
    沈念sama阅读 28,249评论 2赞 250
  • 日本核电站爆炸内幕
    正文 年R本政府宣布，位于F岛的核电站，受9级特大地震影响，放射性物质发生泄漏。R本人自食恶果不足惜，却给世界环境...
    茶点故事阅读 32,864评论 3赞 232
  • 男人毒药：我在死后第九天来索命
    文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹，春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 26,007评论 0赞 8
  • 一桩弑父案，背后竟有这般阴谋
    文/苍兰香墨 我抬头看了看天上的太阳。三九已至，却和暖如春，着一层夹袄步出监牢的瞬间，已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 26,760评论 0赞 192
  • 情欲美人皮
    我被黑心中介骗来泰国打工， 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留，地道东北人。 一个月前我还...
    沈念sama阅读 35,394评论 2赞 269
  • 代替公主和亲
    正文 我出身青楼，却偏偏与公主长得像，于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子，可洞房花烛夜当晚...
    茶点故事阅读 35,281评论 2赞 259

推荐阅读更多精彩内容

  • MySQL EXPLAIN详解
    MySQL EXPLAIN命令是查询性能优化不可缺少的一部分，该文主要讲解explain命令的使用及相关参数说明。...
    学编程的小屁孩阅读 516评论 0赞 0
  • mysql explain详解
    使用EXPLAIN关键字可以模拟优化器执行SQL语句，从而知道MySQL是如何处理你的SQL语句的。可以分析SQL...
    董二弯阅读 761评论 0赞 4
  • MySQL explain详解
    本文主要讲述如何通过 explain 命令获取 select 语句的执行计划，通过 explain 我们可以知道以...
    码农随想录阅读 305评论 0赞 2
  • MySQL explain详解
    Explain简介 本文主要讲述如何通过 explain 命令获取 select 语句的执行计划，通过 expla...
    Java_Explorer阅读 445评论 0赞 1
  • 2019－11－28 周四 阴
    今天感恩节哎，感谢一直在我身边的亲朋好友。感恩相遇！感恩不离不弃。 中午开了第一次的党会，身份的转变要...
    迷月闪星情阅读 10,498评论 0赞 11