Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
Description
InnoDB startup is discovering undo tablespaces in a dirty way. It is reading a possibly stale copy of the TRX_SYS page before processing any redo log records.
A sign of this problem is the buf_pool_invalidate() call in innobase_start_or_create_for_mysql(). It should not be needed at all, and instead, in recv_recovery_from_checkpoint_start() we should assert that the buffer pool is empty before starting to apply redo log records.
Attachments
Issue Links
- blocks
-
MDEV-14481 Execute InnoDB crash recovery in the background
- Closed
-
MDEV-19229 Allow innodb_undo_tablespaces to be changed after database creation
- Closed