MySQL优化之BTree索引使用规则

Wesley13
• 阅读 447

MySQL优化之BTree索引使用规则

从一道题开始分析:

假设某个表有一个联合索引(c1,c2,c3,c4)以下那个只能使用该联合索引的c1,c2,c3部分

explain select * from t where c1='a1' and c2='a2' and c4='a4' and c3='a3';

explain select * from t where c1='a1' and c2='a2' and c4='a4' order by c3;

explain select * from t where c1='a1' and c2='a2' and c4='a4' order by c1;

explain select * from t where c1='a1' and c4='a4'group by c3,c2;

explain select * from t where c1='a1' and c4='a4'group by c2,c3;

explain select * from t where c1='a1' and c4='a4'order by c2,c3;

explain select * from t where c1='a1' and c5='a5' order by c2,c3;

创建表后插入数据:

insert into t
values
('a1','a2','a3','a4','a5'),
('b1','b2','b3','b4','b5');

添加索引:

alter table t add index c1234(c1,c2,c3,c4);

mysql> explain select * from t where c1='a1' and c2='a2' and c4='a4' and c3='a3’;(MySQL执行时会改变其中的位置,c3会在c4的前边)

+----+-------------+-------+------+---------------+-------+---------+-------------------------+------+-----------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref                     | rows | Extra                 |

+----+-------------+-------+------+---------------+-------+---------+-------------------------+------+-----------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 168     | const,const,const,const | 1    | Using index condition |

+----+-------------+-------+------+---------------+-------+---------+-------------------------+------+-----------------------+

1 行于数据集 (0.05 秒)

mysql> explain select * from t where c2='a1' and c3='a4’; (根据索引的左前缀规则,c2,c3部分没有索引)

+----+-------------+-------+------+---------------+------+---------+------+------+-------------+

| id | select_type | table | type | possible_keys | key  | key_len | ref  | rows | Extra       |

+----+-------------+-------+------+---------------+------+---------+------+------+-------------+

| 1  | SIMPLE      | t     | ALL  | NULL          | NULL | NULL    | NULL | 4    | Using where |

+----+-------------+-------+------+---------------+------+---------+------+------+-------------+

1 行于数据集 (0.08 秒)

mysql> explain select * from t where c1='a1' and c2='a2' and c4='a4' order by c3;(根据索引的左前缀规则,order by部分没有索引)

+----+-------------+-------+------+---------------+-------+---------+-------------+------+------------------------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref         | rows | Extra                              |

+----+-------------+-------+------+---------------+-------+---------+-------------+------+------------------------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 84      | const,const | 1    | Using index condition; Using where |

+----+-------------+-------+------+---------------+-------+---------+-------------+------+------------------------------------+

1 行于数据集 (0.08 秒)

mysql> explain select * from t where c1='a1' and c2='a2' and c4='a4' order by c1;(根据索引的左前缀规则,order by使用了索引,可以存在where与order by同时使用索引的情况)

+----+-------------+-------+------+---------------+-------+---------+-------------+------+-----------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref         | rows | Extra                 |

+----+-------------+-------+------+---------------+-------+---------+-------------+------+-----------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 84      | const,const | 1    | Using index condition |

+----+-------------+-------+------+---------------+-------+---------+-------------+------+-----------------------+

1 行于数据集 (0.09 秒)

(以下四组对比,说明在group by 和order by 中,使用索引的顺序,可以避免使用临时表和filesort)

mysql> explain select * from t where c1='a1' and c4=‘a4' group by c3,c2;

+----+-------------+-------+------+---------------+-------+---------+-------+------+---------------------------------------------------------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref   | rows | Extra                                                               |

+----+-------------+-------+------+---------------+-------+---------+-------+------+---------------------------------------------------------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 42      | const | 1    | Using index condition; Using where; Using temporary; Using filesort |

+----+-------------+-------+------+---------------+-------+---------+-------+------+---------------------------------------------------------------------+

1 行于数据集 (0.09 秒)

mysql> explain select * from t where c1='a1' and c4='a4'group by c2,c3;

+----+-------------+-------+------+---------------+-------+---------+-------+------+------------------------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref   | rows | Extra                              |

+----+-------------+-------+------+---------------+-------+---------+-------+------+------------------------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 42      | const | 1    | Using index condition; Using where |

+----+-------------+-------+------+---------------+-------+---------+-------+------+------------------------------------+

1 行于数据集 (0.12 秒)

mysql> explain select * from t where c1='a1' and c4='a4'order by c2,c3;

+----+-------------+-------+------+---------------+-------+---------+-------+------+------------------------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref   | rows | Extra                              |

+----+-------------+-------+------+---------------+-------+---------+-------+------+------------------------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 42      | const | 1    | Using index condition; Using where |

+----+-------------+-------+------+---------------+-------+---------+-------+------+------------------------------------+

1 行于数据集 (0.13 秒)

mysql> explain select * from t where c1='a1' and c5='a5' order by c3,c2;(使用的c1索引)

+----+-------------+-------+------+---------------+-------+---------+-------+------+----------------------------------------------------+

| id | select_type | table | type | possible_keys | key   | key_len | ref   | rows | Extra                                              |

+----+-------------+-------+------+---------------+-------+---------+-------+------+----------------------------------------------------+

| 1  | SIMPLE      | t     | ref  | c1234         | c1234 | 42      | const | 1    | Using index condition; Using where; Using filesort |

+----+-------------+-------+------+---------------+-------+---------+-------+------+----------------------------------------------------+

1 行于数据集 (0.15 秒)

点赞
收藏
评论区
推荐文章
blmius blmius
2年前
MySQL:[Err] 1292 - Incorrect datetime value: ‘0000-00-00 00:00:00‘ for column ‘CREATE_TIME‘ at row 1
文章目录问题用navicat导入数据时,报错:原因这是因为当前的MySQL不支持datetime为0的情况。解决修改sql\mode:sql\mode:SQLMode定义了MySQL应支持的SQL语法、数据校验等,这样可以更容易地在不同的环境中使用MySQL。全局s
Jacquelyn38 Jacquelyn38
2年前
2020年前端实用代码段,为你的工作保驾护航
有空的时候,自己总结了几个代码段,在开发中也经常使用,谢谢。1、使用解构获取json数据let jsonData  id: 1,status: "OK",data: 'a', 'b';let  id, status, data: number   jsonData;console.log(id, status, number )
皕杰报表之UUID
​在我们用皕杰报表工具设计填报报表时,如何在新增行里自动增加id呢?能新增整数排序id吗?目前可以在新增行里自动增加id,但只能用uuid函数增加UUID编码,不能新增整数排序id。uuid函数说明:获取一个UUID,可以在填报表中用来创建数据ID语法:uuid()或uuid(sep)参数说明:sep布尔值,生成的uuid中是否包含分隔符'',缺省为
Wesley13 Wesley13
2年前
MySQL千万级别优化·中
MySQL千万级别的查询优化手段·中单列索引(假设在v\_record表中存在id列的索引)1、WHERE条件使用​EXPLAINSELECT\FROMv\_recordWHEREid2​结论:利用索引进行回表查询2、SELECT字段使用
Easter79 Easter79
2年前
Twitter的分布式自增ID算法snowflake (Java版)
概述分布式系统中,有一些需要使用全局唯一ID的场景,这种时候为了防止ID冲突可以使用36位的UUID,但是UUID有一些缺点,首先他相对比较长,另外UUID一般是无序的。有些时候我们希望能使用一种简单一些的ID,并且希望ID能够按照时间有序生成。而twitter的snowflake解决了这种需求,最初Twitter把存储系统从MySQL迁移
Wesley13 Wesley13
2年前
mysql设置时区
mysql设置时区mysql\_query("SETtime\_zone'8:00'")ordie('时区设置失败,请联系管理员!');中国在东8区所以加8方法二:selectcount(user\_id)asdevice,CONVERT\_TZ(FROM\_UNIXTIME(reg\_time),'08:00','0
Wesley13 Wesley13
2年前
mysql5.6 分页查询优化
mysql5.6分页查询优化场景:表结构:主键(非自增)contentCode(varchar),过滤条件列为updateTime(timeStamp),已经为timestamp建立索引。搜索sql为:SELECTFROMmy_hello_tableWHEREupdat
Wesley13 Wesley13
2年前
MySQL部分从库上面因为大量的临时表tmp_table造成慢查询
背景描述Time:20190124T00:08:14.70572408:00User@Host:@Id:Schema:sentrymetaLast_errno:0Killed:0Query_time:0.315758Lock_
为什么mysql不推荐使用雪花ID作为主键
作者:毛辰飞背景在mysql中设计表的时候,mysql官方推荐不要使用uuid或者不连续不重复的雪花id(long形且唯一),而是推荐连续自增的主键id,官方的推荐是auto_increment,那么为什么不建议采用uuid,使用uuid究
Python进阶者 Python进阶者
3个月前
Excel中这日期老是出来00:00:00,怎么用Pandas把这个去除
大家好,我是皮皮。一、前言前几天在Python白银交流群【上海新年人】问了一个Pandas数据筛选的问题。问题如下:这日期老是出来00:00:00,怎么把这个去除。二、实现过程后来【论草莓如何成为冻干莓】给了一个思路和代码如下:pd.toexcel之前把这