diff options
author | Marko Mäkelä <marko.makela@mariadb.com> | 2022-03-28 11:35:10 +0300 |
---|---|---|
committer | Marko Mäkelä <marko.makela@mariadb.com> | 2022-03-28 11:35:10 +0300 |
commit | b2fa874e462e7352be173a3075a65e49f2fcc404 (patch) | |
tree | 9613dc577960d6e5eb8b5ea3fad15ae9a99bdf56 /scripts/mysql_system_tables_fix.sql | |
parent | 8f8ba758559e473f643baa0a0601d321c42517b9 (diff) | |
download | mariadb-git-b2fa874e462e7352be173a3075a65e49f2fcc404.tar.gz |
MDEV-28181 The innochecksum -w option was inadvertently removed
In commit 7a4fbb55b02b449a135fe935f624422eaacfdd7c (MDEV-25105)
the innochecksum option --write (-w) was removed altogether.
It should have been made a Boolean option, so that old data files
may be converted to a format that is compatible with
innodb_checksum_algorithm=strict_crc32 by executing the following:
innochecksum -n -w ibdata* */*.ibd
It would be better to use an older-version innochecksum
for such a conversion, so that page checksums will be validated
before updating the checksum.
It never was possible for innochecksum to convert files to the
innodb_checksum_algorithm=full_crc32 format that is the default
for new InnoDB data files.
Diffstat (limited to 'scripts/mysql_system_tables_fix.sql')
0 files changed, 0 insertions, 0 deletions