[MDEV-19534] Make innodb_checksum_algorithm=full_crc32 by default, and remove innodb_checksums Created: 2019-05-21  Updated: 2023-11-22  Resolved: 2019-05-22

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.5.0

Type: Task Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: encryption, mariabackup, performance

Issue Links:
Problem/Incident
causes MDEV-27931 A page in innodb_checksum_algorithm=i... Closed
Relates
relates to MDEV-19541 InnoDB crashes when trying to recover... Closed
relates to MDEV-25105 Remove innodb_checksum_algorithm valu... Closed
relates to MDEV-32230 ROW_FORMAT column in I_S.INNODB_SYS_T... Closed
relates to MDEV-12026 Support encrypted SPATIAL INDEX Closed
relates to MDEV-18644 Support FULL_CRC32 for compressed pages. Closed
relates to MDEV-18650 Options deprecated in previous versions Closed
relates to MDEV-20320 Tablespace flags mismatch for full_cr... Closed
relates to MDEV-21568 sys_vars.innodb_checksum_algorithm_ba... Open

 Description   

In MDEV-12026 and MDEV-18644, MariaDB 10.4 introduced support for a new file format innodb_checksum_algorithm=full_crc32. Let us enable it by default in MariaDB 10.5.

At the same time, let us remove the deprecated parameter innodb_checksums.

For now, we will not touch the parameter innodb_log_checksums. InnoDB redo logs use CRC-32C checksums by default already since MariaDB Server version 10.2.2.

 Comments   
Comment by Marko Mäkelä [ 2019-05-21 ]

MDEV-19541 (a crash during the recovery of a corrupted page) was found as part of this effort.

Generated at Thu Feb 08 08:52:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.