--innodb-checksum-algorithm

This page is part of MariaDB's Documentation.

The parent of this page is: mariadbd & mysqld for MariaDB Enterprise Server

Topics on this page:

• Overview

• USAGE

• DETAILS

  • SYNONYMS

  • SCHEMA

  • PARAMETERS

  • SKYSQL

  • PRIVILEGES

• EXAMPLES

• ERROR HANDLING

• FEATURE INTERACTION

• RESPONSES

• DIAGNOSIS

• ISO 9075:2016

• CHANGE HISTORY

• RELATED TOPICS

• EXTERNAL REFERENCES

Overview

• Default value: full_crc32 (MariaDB 10.5 and later)

• Scope: Global

• Dynamic: Yes

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

Old values deprecated in MariaDB 10.3 and removed in MariaDB 10.6:

• 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

For more details see: innodb_checksum_algorithm in the Knowledge Base.

See also: mariadbd & mysqld for MariaDB Enterprise Server 10.6, in 10.5 ES, in 10.4 ES, in 10.3 ES, in 10.2 ES, in 10.6 CS, in 10.5 CS, in 10.4 CS, in 10.3 CS, and in 10.2 CS