Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2
-
None
Description
We should fix MySQL Bug #80788 in MariaDB 10.2.
When I made the InnoDB crash recovery more robust by implementing WL#7142, I also introduced an extra redo log scan pass that could be avoided.
Before MariaDB 10.2 is released as GA, we are free to change the redo log format and add extra information to the redo log checkpoint page, so that the extra scan can be avoided.
Attachments
Issue Links
- is blocked by
-
MDEV-18377 Assertion `!recv_sys->mlog_checkpoint_lsn || *space == TRX_SYS_SPACE || srv_is_undo_tablespace(*space) || it != recv_spaces.end()' failed in recv_parse_log_rec upon prepare from a full backup
- Closed
- relates to
-
MDEV-34802 Recovery fails to note some log corruption
- Closed
-
MDEV-11027 InnoDB log recovery is too noisy
- Closed
-
MDEV-11432 Change the informational redo log format tag to say "MariaDB 10.2.3"
- Closed
-
MDEV-11782 Redefine the innodb_encrypt_log format
- Closed