Status: Closed (View Workflow)
Documentation about innodb_checksum_algorithm is already quite detailed, but still confusing.
strict_: The strict_ options are the same as the regular options, but InnoDB will halt if it comes across a mix of checksum values.
It doesn't specify what exactly counts as a "mix of checksum values".
For example, currently
- if server was bootstrapped with crc32 and then started with strict_innodb, it causes an error on startup (which is probably the above quote means)
- if server was bootstrapped with full_crc32 and then started with strict_innodb, it starts fine.
Possibly it can be explained by the previous description of full_xx specifics, but it does seem to contradict the part about strict_xx.
- relates to
MDEV-12026 Support encrypted SPATIAL INDEX