MDEV-31803 InnoDB aborts during recovery when immediate_scrub_data_uncompressed is enabled
Problem: ======== - InnoDB scans the complete redo log to ensure that there is no corruption and to find the end of the log. During this scan, InnoDB saves all the freed ranges, but it doesn't save recovered size. Later, InnoDB recovery applies partial redo logs and IO thread tries to flush the all freed ranges which was noted during previous complete scan of redo logs. Fix: ==== InnoDB should store the freed pages only when InnoDB stores the redo log records.
Showing
Please register or sign in to comment