[MDEV-19331] Merge new release of InnoDB 5.6.44 to 10.1 Created: 2019-04-25  Updated: 2019-07-23  Resolved: 2019-04-25

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.1.38, 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-fixed

Issue Links:
Blocks
blocks MDEV-20127 Merge new release of InnoDB 5.6.45 to... Closed
PartOf
is part of MDEV-17608 10.1.39 merge Closed
Relates
relates to MDEV-19330 InnoDB ALTER TABLE treats auto_increm... Stalled

 Description   

The following changes between MySQL 5.6.43 and MySQL 5.6.44 touch InnoDB files.

Not applicable (already fixed in MariaDB)

Bug#28867993: POSSIBLE ISSUE WITH MYSQL SERVER RESTART
Already fixed in MariaDB in a less intrusive way.

Bug #29048768 BUILD MYSQL 5.6 WITH GCC7
Already fixed in MariaDB, later also in 5.5 as part of MDEV-13459.

Applicable to MariaDB

Bug #19811005 ALTER TABLE ADD INDEX DOES NOT UPDATE INDEX_LENGTH IN I_S TABLES
This is an one-liner fix to InnoDB persistent statistics, with a test case that fails in MariaDB, possibly due to missing some interface changes.

Bug#28573894 ALTER PARTITIONED TABLE ADD AUTO_INCREMENT DIFF RESULT DEPENDING ON ALGORITHM
This fixes a bug in the InnoDB-native ALTER TABLE for partitioned tables. There are some changes outside InnoDB as well.
Side note: MDEV-19330 is a related upstream bug that affects non-partitioned tables as well.
Generated at Thu Feb 08 08:50:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.