[MySQL]ANALYZE TABLE 更新索引基数

MySQL使用存储的键分布基数来确定表连接顺序
在决定对查询中的特定表使用哪些索引时,也会使用使用键分布基数

ANALYZE TABLE 表名 可以更新表的索引基数,使其更接近非重复的记录数,记录数可以使用show index from 表 来查询cardinality字段

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
mysql> show index from index_test;
+------------+------------+--------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| Table      | Non_unique | Key_name           | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment |
+------------+------------+--------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| index_test |          0 | PRIMARY            |            1 | id          | A         |           5 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | score_index        |            1 | score       | A         |           2 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | name_gid_age_index |            1 | name        | A         |           3 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | name_gid_age_index |            2 | gid         | A         |           3 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | name_gid_age_index |            3 | age         | A         |           6 |     NULL | NULL   |      | BTREE      |         |               |
+------------+------------+--------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
5 rows in set (0.00 sec)
 
mysql> select * from index_test;
+----+------------+-----+-----+-------+
| id | name       | gid | age | score |
+----+------------+-----+-----+-------+
|  1 | taoshihan  |   2 |   0 |     0 |
|  2 | taoshihan1 |   2 |   0 |     0 |
|  3 | taoshihan2 |   3 |  10 |    10 |
|  4 | taoshihan  |   2 |   1 |     0 |
|  5 | taoshihan  |   2 |   2 |     0 |
|  6 | taoshihan  |   2 |   3 |     0 |
+----+------------+-----+-----+-------+
6 rows in set (0.03 sec)
 
mysql> ANALYZE TABLE index_test;
+--------------------+---------+----------+----------+
| Table              | Op      | Msg_type | Msg_text |
+--------------------+---------+----------+----------+
| my_test.index_test | analyze | status   | OK       |
+--------------------+---------+----------+----------+
1 row in set (0.13 sec)
 
mysql> show index from index_test;
+------------+------------+--------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| Table      | Non_unique | Key_name           | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment |
+------------+------------+--------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| index_test |          0 | PRIMARY            |            1 | id          | A         |           6这里变了 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | score_index        |            1 | score       | A         |           2 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | name_gid_age_index |            1 | name        | A         |           3 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | name_gid_age_index |            2 | gid         | A         |           3 |     NULL | NULL   |      | BTREE      |         |               |
| index_test |          1 | name_gid_age_index |            3 | age         | A         |           6 |     NULL | NULL   |      | BTREE      |         |               |
+------------+------------+--------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
5 rows in set (0.07 sec)

  

posted @   唯一客服系统开发笔记  阅读(623)  评论(0编辑  收藏  举报
编辑推荐:
· 开发者必知的日志记录最佳实践
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
阅读排行:
· 阿里最新开源QwQ-32B,效果媲美deepseek-r1满血版,部署成本又又又降低了!
· 开源Multi-agent AI智能体框架aevatar.ai,欢迎大家贡献代码
· Manus重磅发布:全球首款通用AI代理技术深度解析与实战指南
· 被坑几百块钱后,我竟然真的恢复了删除的微信聊天记录!
· AI技术革命,工作效率10个最佳AI工具
历史上的今天:
2019-02-27 [Go] golang连接查询mysql
2019-02-27 [日常] 解决mysql不允许外部访问
2016-02-27 [android] android下junit测试框架配置
2016-02-27 [android] 测试的相关概念
点击右上角即可分享
微信分享提示
1
chat with us