MySQL 8.0版本计划

MySQL 8.0开始采用快速迭代开发模式,基本上是每隔3个月就发布一个新的小版本。去年1月18日(2022.1.18)发布MySQL 8.0.28,今年1月17日发布MySQL 8.0.32,再看看其他几个版本的时间,还真是贼守时啊。



版本

发布时间

上一年版本

上一年发布时间

8.0.32

2023.1.17

8.0.28

2022.1.18

8.0.31

2022.10.11

8.0.27

2021.10.10

8.0.30

2022.7.26

8.0.26

2021.7.20

8.0.29

2022.4.26

8.0.25

2021.5.11



在这中间,出了点小意外,MySQL 8.0.29因为存在严重安全问题,刚上架没多久就被下架了,可以看下这篇文章的解读:MySQL8.0.29出现重大bug,现已下架。

MySQL 8.0.32的一些变化

总的来说,8.0.32版本基本上属于修修补补状态,乏善可陈。

在这里,主要罗列我个人认为需要关注的几个要点或bug fix,想看详细变化的可以查看 MySQL 8.0.32 Release Notes, https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-32.html。

  • 当数据表名用 "$" 开头的话,引用时必须用反引号 "`",否则会有一个WARN,例如:
mysql> create table $t1(id int primary key);

 


Query OK, 0 rows affected, 1 warning (0.02 sec)

 


 

 


mysql> show warnings;

 


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

 


| Level   | Code | Message                                                                                                     |

 


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

 


| Warning | 1681 | '$ as the first character of an unquoted identifier' is deprecated and will be removed in a future release. |

 


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

 


 

 


mysql> table $t1;

 


+----+

 


| id |

 


+----+

 


|  1 |

 


|  2 |

 


+----+

 



2 rows in set, 1 warning (0.00 sec)

 


 

 


mysql> show warnings;

 


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

 


| Level   | Code | Message                                                                                                     |

 


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

 


| Warning | 1681 | '$ as the first character of an unquoted identifier' is deprecated and will be removed in a future release. |

 


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

 


 

 


mysql> table `$t1`; -- 加上反引号 "`" 就不再报告WARN

 


+----+

 


| id |

 


+----+

 


|  1 |

 


|  2 |

 


+----+

 



2 rows in set (0.00 sec)
  • 部分客户端程序采用新的压缩参数(--compression-algorithms=zstd|zlib|uncompressed)替换旧参数(--compress),新参数中可以指定不同压缩算法或不压缩。影响的客户端程序有:mysqlpump, mysqlcheck, mysql, mysqladmin, mysqlbinlog, mysqldump, mysqlimport, mysqlshow, mysqlslap, mysql_upgrade, mysqltest,而企业版备份工具mysqlbackup暂时不受影响,还采用 --compress 参数。例如:
$ /usr/local/mysql-8.0.32-linux-glibc2.17-x86_64-minimal/bin/mysqldump --set-gtid-purged=OFF -S./mysql.sock --compress test > test.sql

 


WARNING: --compress is deprecated and will be removed in a future version. Use --compression-algorithms instead.

 


 

 


$ /usr/local/mysql-8.0.32-linux-glibc2.17-x86_64-minimal/bin/mysql --compress -S./mysql.sock

 


WARNING: --compress is deprecated and will be removed in a future version. Use --compression-algorithms instead.
  • 新增选项 explain_format 用于设置 EXPLAIN 查看执行计划时的默认输出格式,支持 JSON, TREE, TRADITIONAL(或者写成 DEFAULT 也可以);当设置为 JSON 格式时,执行 EXPLAIN ANALYZE 则会报错:
mysql> set @@explain_format = json;

 


Query OK, 0 rows affected (0.00 sec)

 


 

 


mysql> explain analyze select * from t1;

 


ERROR 1235 (42000): This version of MySQL doesn't yet support 'EXPLAIN ANALYZE with JSON format'

原来的 EXPLAIN FORMAT=? 语法仍然支持,但不支持设置为 DEFAULT,只能写成 TRADITIONAL:

mysql> explain format=tree select * from t1;

 


...

 


mysql> explain format=json select * from t1;

 


...

 


mysql> explain format=traditional select * from t1;

 


...

 


mysql> explain format=default select * from t1;

 


ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'default select * from t1' at line 1
  • 在MGR中设置 group_replication_consistency = AFTER,当某个Secondary节点因为网络不稳定时,可能会触发报错 Transaction 'GTID' does not exist on Group Replication consistency manager while receiving remote transaction prepare.。这是因为事务event在 View_change_log_event 后写入导致。在8.0.32中,修复了这个问题,将事务event先于 View_change_log_event 写入,就可以避免该问题。不过要再次强调,MGR中强烈建议不要设置为 AFTER模式,具体可以参考这篇文章:为什么MGR一致性模式不推荐AFTER。
  • 当从MySQL 5.7升级到8.0时,如果某个库中有大量的表,内存可能会消耗过多内存。这是因为在升级时,一次性读取所有表并执行 CHECK TABLE .. FOR UPGRADE。在8.0.32中,调整为逐个表检查是否可升级,就可以避免这个问题了。

有些bug fix的描述信息比较少,或者指向内部bug id无法看到细节,这里就不再罗列了。

延伸阅读

  • MySQL 8.0.32 GA
  • Changes in MySQL 8.0.32, https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-32.html
  • Server System Variables - explain_format, https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_explain_format
  • EXPLAIN Statement, https://dev.mysql.com/doc/refman/8.0/en/explain.html#explain-execution-plan

Enjoy MySQL :)


《深入浅出MGR》视频课程

戳此小程序即可直达B站

https://www.bilibili.com/medialist/play/1363850082?business=space_collection&business_id=343928&desc=0