[MDEV-28417] Merge new release of InnoDB 5.7.38 to 10.2 Created: 2022-04-26  Updated: 2022-07-26  Resolved: 2022-04-27

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9
Fix Version/s: 10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3, 10.9.1

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

Issue Links:
Blocks
blocks MDEV-29165 Merge new release of InnoDB 5.7.39 to... Closed
is blocked by MDEV-27539 Merge new release of InnoDB 5.7.37 to... Closed
PartOf
includes MDEV-28415 ALTER TABLE on a large table hangs In... Closed
includes MDEV-28416 Incorrect AUTO_INCREMENT may be issue... Closed

 Description   

MySQL 5.7.38 includes the following InnoDB changes:

Not applicable to MariaDB Server

BUG #33459653 : coredump after add index for partion table with ibd file missing
The included test case produces an error HA_ERR_TABLESPACE_MISSING from ha_innobase::open() for the missing data file of the partition.
The code fix is for the refactored MySQL 5.7 “native partitioning” (ha_innopart), which never existed in MariaDB Server.
Bug #33600109 Segmentation fault at ha_innobase::index_type, Improper code handling
This duplicates MDEV-22928. No test case is included.
BUG #32586721 : SERVER CRASH IN FIL_SPACE_IS_BEING_TRUNCATED
The affected function fil_space_is_being_truncated() (which performs a redundant tablespace lookup) was removed from MariaDB as part of a fix of MDEV-11202. The test case involves encrypted tablespaces, which Oracle implemented in MySQL 5.7 differently in response to MariaDB Server 10.1.

Applicable to MariaDB Server

Bug #33101844 CREATE FULLTEXT INDEX CRASHES SERVER FOR LARGE TABLE
Filed as MDEV-28415.
Bug 26906787 - INCORRECT AUTO_INCREMENT IDS ISSUED WHEN CLOSE TO ULLONG_MAX
Filed as MDEV-28416.


Generated at Thu Feb 08 10:00:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.