Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
-
None
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.
Attachments
Issue Links
- blocks
-
MDEV-29165 Merge new release of InnoDB 5.7.39 to 10.3
- Closed
- includes
-
MDEV-28415 ALTER TABLE on a large table hangs InnoDB
- Closed
-
MDEV-28416 Incorrect AUTO_INCREMENT may be issued when close to UINT64_MAX
- Closed
- is blocked by
-
MDEV-27539 Merge new release of InnoDB 5.7.37 to 10.2
- Closed