Details
- 
    Task 
- 
    Status: Closed (View Workflow)
- 
    Major 
- 
    Resolution: Fixed
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.
Attachments
Issue Links
- causes
- 
                    MDEV-27931 A page in innodb_checksum_algorithm=innodb is wrongly claimed to be corrupted -         
- Closed
 
-         
- relates to
- 
                    MDEV-19541 InnoDB crashes when trying to recover a corrupted page -         
- Closed
 
-         
- 
                    MDEV-25105 Remove innodb_checksum_algorithm values none, innodb, strict_none, strict_innodb -         
- Closed
 
-         
- 
                    MDEV-32230 ROW_FORMAT column in I_S.INNODB_SYS_TABLESPACES is NULL for innodb_checksum_algorithm=full_crc32 tablespaces -         
- Closed
 
-         
- 
                    MDEV-33808 InnoDB: Unable to read page [page id: space=0, page number=5] into the buffer pool after 100 -         
- Closed
 
-         
- 
                    MDEV-12026 Support encrypted SPATIAL INDEX -         
- Closed
 
-         
- 
                    MDEV-18644 Support FULL_CRC32 for compressed pages. -         
- Closed
 
-         
- 
                    MDEV-18650 Options deprecated in previous versions -         
- Closed
 
-         
- 
                    MDEV-20320 Tablespace flags mismatch for full_crc32 format -         
- Closed
 
-         
- 
                    MDEV-21568 sys_vars.innodb_checksum_algorithm_basic failed in buildbot with errno: 2000 -         
- Closed
 
-