innodb_checksum_algorithm

Overview

In 10.6 ES, 10.6 CS:

The algorithm InnoDB uses for page checksumming. Possible values are FULL_CRC32 for new files, always use CRC-32C; for old, see CRC32 below; STRICT_FULL_CRC32 for new files, always use CRC-32C; for old, see STRICT_CRC32 below; CRC32 write crc32, allow any of the other checksums to match when reading; STRICT_CRC32 write crc32, do not allow other algorithms to match when reading; INNODB write a software calculated checksum, allow any other checksums to match when reading; STRICT_INNODB write a software calculated checksum, do not allow other algorithms to match when reading; NONE write a constant magic number, do not do any checksum verification when reading; STRICT_NONE write a constant magic number, do not allow values other than that magic number when reading; Files updated when this option is set to crc32 or strict_crc32 will not be readable by MariaDB versions older than 10.0.4; new files created with full_crc32 are readable by MariaDB 10.4.3+

In 10.6 ES:

The algorithm InnoDB uses for page checksumming. Possible values are FULL_CRC32 for new files, always use CRC-32C; for old, see CRC32 below; STRICT_FULL_CRC32 for new files, always use CRC-32C; for old, see STRICT_CRC32 below; CRC32 write crc32, allow any of the other checksums to match when reading; STRICT_CRC32 write crc32, do not allow other algorithms to match when reading; INNODB write a software calculated checksum, allow any other checksums to match when reading; STRICT_INNODB write a software calculated checksum, do not allow other algorithms to match when reading; NONE write a constant magic number, do not do any checksum verification when reading; STRICT_NONE write a constant magic number, do not allow values other than that magic number when reading; Files updated when this option is set to crc32 or strict_crc32 will not be readable by MariaDB versions older than 10.0.4; new files created with full_crc32 are readable by MariaDB 10.4.3+

In 10.5 ES, 10.5 CS, 10.4 ES, 10.4 CS:

The algorithm InnoDB uses for page checksumming. Possible values are FULL_CRC32 for new files, always use CRC-32C; for old, see CRC32 below; STRICT_FULL_CRC32 for new files, always use CRC-32C; for old, see STRICT_CRC32 below; CRC32 write crc32, allow any of the other checksums to match when reading; STRICT_CRC32 write crc32, do not allow other algorithms to match when reading; INNODB write a software calculated checksum, allow any other checksums to match when reading; STRICT_INNODB write a software calculated checksum, do not allow other algorithms to match when reading; NONE write a constant magic number, do not do any checksum verification when reading (same as innodb_checksums=OFF); STRICT_NONE write a constant magic number, do not allow values other than that magic number when reading; Files updated when this option is set to crc32 or strict_crc32 will not be readable by MariaDB versions older than 10.0.4; new files created with full_crc32 are readable by MariaDB 10.4.3+

In 10.5 ES, 10.4 ES:

The algorithm InnoDB uses for page checksumming. Possible values are FULL_CRC32 for new files, always use CRC-32C; for old, see CRC32 below; STRICT_FULL_CRC32 for new files, always use CRC-32C; for old, see STRICT_CRC32 below; CRC32 write crc32, allow any of the other checksums to match when reading; STRICT_CRC32 write crc32, do not allow other algorithms to match when reading; INNODB write a software calculated checksum, allow any other checksums to match when reading; STRICT_INNODB write a software calculated checksum, do not allow other algorithms to match when reading; NONE write a constant magic number, do not do any checksum verification when reading (same as innodb_checksums=OFF); STRICT_NONE write a constant magic number, do not allow values other than that magic number when reading; Files updated when this option is set to crc32 or strict_crc32 will not be readable by MariaDB versions older than 10.0.4; new files created with full_crc32 are readable by MariaDB 10.4.3+

In 10.3 ES, 10.3 CS, 10.2 ES, 10.2 CS:

The algorithm InnoDB uses for page checksumming. Possible values are CRC32 (hardware accelerated if the CPU supports it) write crc32, allow any of the other checksums to match when reading; STRICT_CRC32 write crc32, do not allow other algorithms to match when reading; INNODB write a software calculated checksum, allow any other checksums to match when reading; STRICT_INNODB write a software calculated checksum, do not allow other algorithms to match when reading; NONE write a constant magic number, do not do any checksum verification when reading (same as innodb_checksums=OFF); STRICT_NONE write a constant magic number, do not allow values other than that magic number when reading; Files updated when this option is set to crc32 or strict_crc32 will not be readable by MariaDB versions older than 10.0.4

DETAILS

PARAMETERS

Command-line

--innodb_checksum_algorithm={crc32|strict_crc32|full_crc32|strict_full_crc32}

Configuration file

Supported

Dynamic

Yes

Scope

Global

Data Type

ENUM (crc32, strict_crc32, full_crc32, strict_full_crc32)

Default Value

full_crc32

SKYSQL

Cloud

SkySQL Topology

ES Ver

Default

AWS

Multi-Node Analytics

10.6

full_crc32

Single Node Analytics

10.6

full_crc32

Distributed Transactions

10.5

Not present

10.6

Not present

Replicated Transactions

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

Single Node Transactions

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

GCP

Multi-Node Analytics

10.6

full_crc32

Single Node Analytics

10.6

full_crc32

Distributed Transactions

10.5

Not present

10.6

Not present

Replicated Transactions

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

Single Node Transactions

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

Cloud

SkySQL Topology

ES Ver

Default

AWS

ColumnStore Data Warehouse

10.6

full_crc32

Xpand Distributed SQL

10.5

Not present

10.6

Not present

Enterprise Server With Replica(s)

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

Enterprise Server Single Node

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

GCP

ColumnStore Data Warehouse

10.6

full_crc32

Xpand Distributed SQL

10.5

Not present

10.6

Not present

Enterprise Server With Replica(s)

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

Enterprise Server Single Node

10.4

full_crc32

10.5

full_crc32

10.6

full_crc32

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Default value changed in MariaDB Community Server 10.5.0 from crc32 to full_crc32

10.4 Enterprise

  • Default value changed in MariaDB Enterprise Server 10.4.6-1 from crc32 to full_crc32

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

  • Default value changed in MariaDB Community Server 10.2.2 from INNODB to crc32

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.4 Enterprise

  • Default value changed in MariaDB Enterprise Server 10.4.6-1 from crc32 to full_crc32

EXTERNAL REFERENCES