[MDEV-17536] Merge new release of InnoDB 5.7.24 to 10.2 Created: 2018-10-24  Updated: 2020-10-27  Resolved: 2018-10-25

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3
Fix Version/s: 10.3.11, 10.2.19

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

Issue Links:
Blocks
blocks MDEV-18338 Merge new release of InnoDB 5.7.25 to... Closed
is blocked by MDEV-16850 Merge new release of InnoDB 5.7.23 to... Closed
is blocked by MDEV-17541 KILL QUERY during lock wait in FOREIG... Closed
is blocked by MDEV-17545 Predicate lock for SPATIAL INDEX shou... Closed
is blocked by MDEV-17546 SPATIAL INDEX should not be allowed f... Closed
is blocked by MDEV-17548 Incorrect access to off-page column f... Closed

 Description   

MySQL 5.7.24 includes the following InnoDB changes:

Not applicable to MariaDB:

Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213 is not applicable, because we already removed the TrxInInnoDB code and trx->lock.start_stmt in MDEV-13935.
Post Push fix for test case failure innodb_gis.rtree_rollback1 on weekly-5.7 is a follow-up fix for a change in MySQL 5.7.23. My rewrite of that fix MDEV-14637 did not break SPATIAL INDEX handling.
Bug#26375771: INNODB: ASSERTION FAILURE: MACH0DATA.IC:308:VAL > 0X7F is a fix for online table rebuild when virtual columns exist and the table is in ROW_FORMAT=REDUNDANT. MDEV-13795/MDEV-14332 in MariaDB blocked the online table rebuild when the table contains indexed virtual columns.
Bug #27921932 UPDATING ROW WITH GENERATED COLUMN DURING ALTER TABLE RESULTS IN BROCKEN DATA is another fix for online table rebuild when indexed virtual columns exist.

Bug#28104394 - INNODB 5.7 PRIMARY KEY SCAN LACK DATA is one more fix for the "optimized range scan" series of regressions caused by a change that we decided not to merge to MariaDB in MDEV-11751.
Bug#27903881 - FIL_SPACE_GET(TABLE->SPACE) != __NULL and Bug#27798708 ALTER TABLE CRASHES: ASSERTION FAILURE: DICT0DICT.CC:1420: UT_A(TABLE2 == NULL) affect only the "native InnoDB partitioning" that MariaDB did not merge from MySQL 5.7.
Bug #27804668 CRASH DUE TO SEGMENTATION FAULT IN FIL_SPACE_IS_BEING_TRUNCATED is a regression caused by a change that I cherry-picked to MariaDB 10.2.8 in a way that is not affected. (MariaDB checks fil_space_t* for NULL before dereferencing it.)
wl#11571 : Deprecate Shared tablespaces in partitioned table and WL#12179 Deprecate TABLESPACE=innodb_file_per_table and TABLESPACE=innodb_temporary phrases while creating temporary tables do not apply, because MariaDB does not support CREATE TABLESPACE for InnoDB.

Applicable to MariaDB

Bug #28068293 KILLING QUERY THAT IS WAITING FOR LOCK VIA FOREIGN KEY CAUSES MYSQL CRASH will be fixed in MDEV-17541.

Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE will be fixed in MDEV-17545.

Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE() will be fixed in MDEV-17546.

Bug #27968952 INNODB CRASH/CORRUPTION WITH TEXT PREFIX INDEXES will be fixed in MDEV-17548.


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