mariadb/storage/innobase/log
Thirunarayanan Balathandayuthapani 4bedb222a8 MDEV-36304 InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY error
during mariabackup --prepare

Reason:
======
During --prepare of partial backup, if InnoDB encounters the redo log
for the excluded tablespace then InnoDB stores the space id in dirty
tablespace list during recovery, anticipates that it may encounter
FILE_* redo log records in the future. Even though we encounter FILE_*
record for the partial excluded tablespace then we fail to replace the
name in dirty tablespace list. This lead to missing of
FILE_* redo log records error.

Solution:
========
fil_name_process(): Rename the file name from "" to name encountered
during FILE_* record

recv_init_missing_space(): Correct the condition to print the warning
message of missing tablespace during mariabackup restore process.
2025-04-22 17:53:08 +05:30
..
log0crypt.cc Merge 10.5 into 10.6 2021-06-23 09:24:32 +03:00
log0log.cc MDEV-35171 OS_FILE_NORMAL and OS_FILE_AIO are misleading 2024-10-21 15:31:32 +02:00
log0recv.cc MDEV-36304 InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY error 2025-04-22 17:53:08 +05:30
log0sync.cc Merge 10.5 into 10.6 2024-06-07 10:03:51 +03:00
log0sync.h MDEV-26789 log_write_up_to needs mechanism to prevent stalls of async. waiters 2021-10-08 13:18:59 +02:00