Marko Mäkelä 0b25551a61 MDEV-29999 innodb_undo_log_truncate=ON is not crash safe ... If a log checkpoint occurs at the end LSN of mtr.commit_shrink(space) in trx_purge_truncate_history(), then recovery may fail because it could try to apply too old log records to too old copies of undo log pages. This was repeated with the following test: ./mtr innodb.undo_log_truncate,4k,strict_full_crc32 recv_sys_t::trim(): Move some code to the caller. recv_sys_t::apply(): For undo tablespace truncation, discard all old redo log for the undo tablespace, and then truncate the file to the desired size. Tested by: Matthias Leich		2022-11-15 16:56:13 +02:00
..
log0crypt.cc	Merge 10.4 into 10.5	2021-06-23 08:17:49 +03:00
log0log.cc	MDEV-29982 Improve the InnoDB log overwrite error message	2022-11-14 12:18:03 +02:00
log0recv.cc	MDEV-29999 innodb_undo_log_truncate=ON is not crash safe	2022-11-15 16:56:13 +02:00
log0sync.cc	MDEV-21534 fixup: Use a compile-time constant	2020-11-20 07:59:41 +02:00
log0sync.h	MDEV-21534 - Improve innodb redo log group commit performance	2020-03-01 19:02:21 +01:00