Bug #49852 | make innodb checksum faster | ||
---|---|---|---|
Submitted: | 21 Dec 2009 17:43 | Modified: | 14 Oct 2011 17:34 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S4 (Feature request) |
Version: | 5.0,5.1,5.1 plugin | OS: | Any |
Assigned to: | Calvin Sun | CPU Architecture: | Any |
Tags: | checksum, innodb, performance |
[21 Dec 2009 17:43]
Mark Callaghan
[23 Dec 2009 14:05]
Valeriy Kravchuk
Thank you for the feature request.
[14 Oct 2011 17:34]
John Russell
Added to 5.6.3 changelog: You can improve the efficiency of the InnoDB checksum feature by specifying the configuration option innodb_checksum_algorithm=crc32, which turns on a faster checksum algorithm. This option replaces the innodb_checksums option. Data written using the old checksum algorithm (option value innodb) is fully upward-compatible; tablespaces modified using the new checksum algorithm (option value crc32) cannot be downgraded to an earlier version of MySQL that does not support the innodb_checksum_algorithm option. See for details.