Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
In MySQL 5.7 (and MariaDB 10.2.2 onwards), the InnoDB redo log is not self-contained with respect to some DDL operations.
Most notably, WL#7277 disables the redo logging of data pages in the initial phase of ALTER TABLE…ALGORITHM=INPLACE. (The online_log apply is still being redo-logged.) The presence of a MLOG_INDEX_LOAD record indicates that some data was omitted from the redo log.
Percona implements a workaround. We should look at their implementation.
MDEV-13564 mentions another class of operations that makes the redo log not self-contained: TRUNCATE TABLE and undo tablespace truncation.
Attachments
Issue Links
- causes
-
MDEV-13802 mariabackup --lock-ddl-per-table fails when table names contain backticks
- Closed
-
MDEV-13825 mariabackup --lock-ddl-per-table does not properly lock FULLTEXT auxiliary tables
- Closed
- relates to
-
MDEV-13564 TRUNCATE TABLE and undo tablespace truncation are not compatible with Mariabackup
- Closed
-
MDEV-16809 Allow full redo logging for ALTER TABLE
- Closed
-
MDEV-14545 Backup fails due to MLOG_INDEX_LOAD record
- Closed