mariadb/storage/innobase/fsp
Marko Mäkelä 4beace3316 MDEV-21171 InnoDB is unnecessarily resetting FIL_PAGE_TYPE for full_crc32 files
Before commit c0f47a4a58 (MDEV-12026)
introduced the innodb_checksum_algorithm=full_crc32 format,
it was impossible to tell if InnoDB data files contained garbage in
the FIL_PAGE_TYPE header field (and possibly other fields).
This is because before commit 3926673ce7
in MySQL 5.1.48, InnoDB would write uninitialized data to some fields,
and because there was no way to tell with which InnoDB version a data
file was created.

If fil_space_t::full_crc32() holds, the data file cannot contain
uninitialized garbage or invalid FIL_PAGE_TYPE, and thus
fil_block_check_type() should not be invoked to correct anything.
2019-11-28 16:22:53 +02:00
..
fsp0file.cc MDEV-13564 follow-up: Remove dead code 2019-09-26 10:25:34 +03:00
fsp0fsp.cc MDEV-21171 InnoDB is unnecessarily resetting FIL_PAGE_TYPE for full_crc32 files 2019-11-28 16:22:53 +02:00
fsp0space.cc Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00
fsp0sysspace.cc Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00