[MDEV-33308] CHECK TABLE is resetting TABLE_SHARE::mysql_version even if --read-only Created: 2024-01-25  Updated: 2024-02-08

Status: Confirmed
Project: MariaDB Server
Component/s: Server, Upgrades
Affects Version/s: 10.5, 10.6, 10.11
Fix Version/s: 10.5, 10.6, 10.11

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Unresolved Votes: 0
Labels: upgrade

Issue Links:
Relates
relates to MDEV-33277 In-place migration from MySQL 5.7 cau... Stalled

 Description   

While constructing the test innodb.autoinc_import for my proposed fix of MDEV-33277, I was surprised to find out that CHECK TABLE would modify the contents of .frm files. If you enable the commented-out CHECK TABLE statement in the test, it will fail because on the next server restart (in read-write mode) the TABLE_SHARE::mysql_version for all affected tables would be MYSQL_VERSION_ID, that is, the current server version. That is, the files that had been copied from mysql-test/std_data/autoinc_import*.frm had been modified by the CHECK TABLE statement.

I might understand this if the statement were CHECK TABLE...FOR UPGRADE, but even that command should in my opinion honour the parameter --read-only.



 Comments   
Comment by Marko Mäkelä [ 2024-01-30 ]

This will be fixed as part of the MDEV-33277 fix.

Generated at Thu Feb 08 10:37:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.