[MDEV-19342] Merge new release of InnoDB 5.7.26 to 10.2 Created: 2019-04-26  Updated: 2020-02-24  Resolved: 2019-04-26

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3, 10.4
Fix Version/s: 10.2.24, 10.3.15, 10.4.5

Type: Bug Priority: Blocker
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: upstream

Issue Links:
Blocks
blocks MDEV-20133 Merge new release of InnoDB 5.7.27 to... Closed
is blocked by MDEV-18338 Merge new release of InnoDB 5.7.25 to... Closed
Relates
relates to MDEV-17603 Allow statement-based replication for... Closed
relates to MDEV-17614 INSERT on dup key update is replicat... Closed

 Description   

MySQL 5.7.26 includes the following InnoDB changes:

Applicable to MariaDB

Bug#27850600 INNODB ASYNC IO ERROR HANDLING IN IO_EVENT
This fixes incorrect error handling for the Linux libaio io_getevent().

Bug#29021730 CRASHING INNOBASE_COL_CHECK_FK WITH FOREIGN KEYS
There is no test case, and I failed to construct one. It looks like this bug could affect MariaDB.

Not applicable to MariaDB

Bug#29007731 ASSERTION FAILURE: FIL0FIL.CC.*SPACE->N_PENDING_FLUSHES == 0
This appears to be a follow-up fix to the MySQL counterpart of MDEV-18349. I was unable to repeat any assertion failures on MariaDB when running the following:

./mtr --big-test --parallel=auto --mysqld=--loose-innodb-flush-method=O_DIRECT_NO_FSYNC

The MySQL change is only removing debug assertions. I think that it is safe to keep those assertions for now, even if they could fail in MariaDB debug builds.

Bug#25966845 INSERT ON DUPLICATE KEY GENERATE A DEADLOCK
MariaDB already fixed much of this in MDEV-17073. This change conflicts with MDEV-17614 (which fixed the replication bug). MDEV-17603 would fix and re-enable statement-based replication.

Bug#28825718 - ASSERTION FAILURE: TRX0REC.CC:NNN:N_IDX > 0 WHILE DOING REPLACE/INSERT
This bug had already been fixed in MDEV-12004.

Bug #29207450 TINYTEXT COLUMN TAKES LONG TIME IN THE GROUP BY OPERATION
MDEV-11487 removed the code from MariaDB.

Bug#27373959 CREATE TABLE PANIC ON INNOBASE_PARSE_HINT_FROM_COMMENT
Already fixed in MDEV-15865.

 Comments   
Comment by Marko Mäkelä [ 2019-08-12 ]

MDEV-17614 will flag INSERT…ON DUPLICATE KEY UPDATE unsafe for statement-based replication when there are multiple unique indexes.

Thanks to this, we can remove the logic that was mostly disabled in MDEV-17073 already. The related MDEV-17603 is only a performance optimization that would allow statement-based replication by logging more information.

Generated at Thu Feb 08 08:50:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.