tencent cloud

Crash Caused by a Redo Buffer Calculation Defect in Instant CHANGE COLUMN
Last updated:2025-12-24 16:09:19
Crash Caused by a Redo Buffer Calculation Defect in Instant CHANGE COLUMN
Last updated: 2025-12-24 16:09:19

Issue

A redo buffer calculation defect in the instant CHANGE COLUMN operation causes a crash.

Issue Triggering Scenarios

To calculate the size of log indexes, changes in column order should be considered, and the size of index information should also be recorded in the redo log. Originally, these columns were not accounted for. Performing an UPDATE operation immediately after executing an ALTER TABLE statement to modify column order causes a crash due to miscalculated redo log space.

Affected Kernel Versions

MySQL 8.0 20230704 and earlier versions.

Fixed Kernel Version

MySQL 8.0 20241005.

Check Methods

You can refer to the following commands to check for tables with potential risks.
select replace(name, '/', '.') as 'table_schema.table_name' from information_schema.innodb_tables where TOTAL_ROW_VERSIONS!=0 or INSTANT_COLS!=0;

Fixing Methods

1. Upgrade the kernel version to MySQL 8.0 20241005. For the operation method, see Upgrading the Kernel Minor Version.
2. After a kernel version upgrade, rebuild and repair the corrupted tables. You can use the method alter table xx engine = innodb; for repair. To avoid business impact caused by table locking, it is recommended to perform the repair during off-peak hours using tools such as pt-osc.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback