Persona MySQL 26.7: A New Versioning Era Begins
MySQL 26.7 improves the robustness of InnoDB undo tablespace truncation. Previously, InnoDB used a separate undo_{space_number}_trunc.log file to keep track of an undo tablespace truncation operation. This external file…
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
MySQL 26.7 improves the robustness of InnoDB undo tablespace truncation. Previously, InnoDB used a separate undo_{space_number}_trunc.log file to keep track of an undo tablespace truncation operation. This external file was used to determine whether a truncation operation was in progress, particularly during recovery.
Now this approach has changed: instead of maintaining a separate truncate log file, the truncation state is captured directly in the undo tablespace header.
This improves both undo truncation and recovery as it does not rely on a separate dedicated file.
There were some internal changes, or rather improvements, to the structure and efficiency of the core InnoDB recovery, metadata, redo-log, tablespace, and transaction-visibility code paths.
This doesn’t bring any changes to the usage point of view. The goal is to make these components easier to maintain, test, and extend without changing user-visible SQL semantics.
The group_replication_communication_stack now defaults to “MySQL” from “XCOM”. This change is more aligned with the MySQL Server authentication and connection security.
This also means no separate communication port needs to be specified for group replication variables (group_replication_local_address and group_replication_group_seeds). The native MySQL port (3306)/ MEMBER_PORT or whatever is defined for MySQL nodes can be used instead.
In short, the default MySQL communication stack provides the benefits below.
Note – If migrating from the old environment or switching from “XCOM” to “MySQL” simply switching the communication stack wouldn’t work.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。