mariadb/storage/innobase/buf
Marko Mäkelä e0e096faaa MDEV-29982 Improve the InnoDB log overwrite error message
The InnoDB write-ahead log ib_logfile0 is of fixed size,
specified by innodb_log_file_size. If the tail of the log
manages to overwrite the head (latest checkpoint) of the log,
crash recovery will be broken.

Let us clarify the messages about this, including adding
a message on the completion of a log checkpoint that notes
that the dangerous situation is over.

To reproduce the dangerous scenario, we will introduce the
debug injection label ib_log_checkpoint_avoid_hard, which will
avoid log checkpoints even harder than the previous
ib_log_checkpoint_avoid.

log_t::overwrite_warned: The first known dangerous log sequence number.
Set in log_close() and cleared in log_write_checkpoint_info(),
which will output a "Crash recovery was broken" message.
2022-11-14 12:18:03 +02:00
..
buf0block_hint.cc Merge 10.4 into 10.5 2020-10-30 11:15:30 +02:00
buf0buddy.cc Merge 10.4 to 10.5 2020-10-22 17:08:49 +03:00
buf0buf.cc Merge 10.4 into 10.5 2022-11-08 17:01:28 +02:00
buf0checksum.cc Merge 10.4 into 10.5 2019-05-23 10:32:21 +03:00
buf0dblwr.cc Fix clang -Wunused-but-set-variable 2022-04-21 11:35:07 +03:00
buf0dump.cc MDEV-26547 fixup: Wait for read completion 2021-09-07 08:55:08 +03:00
buf0flu.cc MDEV-29982 Improve the InnoDB log overwrite error message 2022-11-14 12:18:03 +02:00
buf0lru.cc MDEV-26200 buf_pool.flush_list corrupted by buffer pool resizing or ROW_FORMAT=COMPRESSED 2021-07-22 10:05:13 +03:00
buf0rea.cc MDEV-27900: aio handle partial reads/writes 2022-03-12 09:47:53 +11:00