[#MDEV-20127] Merge new release of InnoDB 5.6.45 to 10.1

[MDEV-20127] Merge new release of InnoDB 5.6.45 to 10.1 Created: 2019-07-23 Updated: 2019-10-30 Resolved: 2019-07-23
Status:	Closed
Project:	MariaDB Server
Component/s:	Storage Engine - InnoDB, Storage Engine - XtraDB
Fix Version/s:	10.2.26, 10.1.41, 10.3.17, 10.4.7

Type:

Task

Priority:

Blocker

Reporter:

Marko Mäkelä

Assignee:

Marko Mäkelä

Resolution:

Fixed

Votes:

Labels:

None

Issue Links:

Blocks
is blocked by	~~MDEV-19331~~	Merge new release of InnoDB 5.6.44 to...	Closed
PartOf
is part of	~~MDEV-19565~~	10.4.7 merge	Closed
Relates
relates to	MDEV-20126	Semaphore timeout due to large fullte...	Open
relates to	~~MDEV-20927~~	Duplicate key with auto increment	Closed

Description

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

The hidden head of the MySQL 5.5 branch

Revert a problematic auto_increment_increment ‘fix’ from 2014. This involves replacing the ~~MDEV-8827~~ fix (1, 2) and in 10.1, removing some WSREP instrumentation.

Bug#28104394 : INNODB 5.7 PRIMARY KEY SCAN LACK DATA
This 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 #25289359 DML/DDL ON LARGE FULLTEXT TABLES CAUSE SEMAPHORE TIMEOUTS AND ASSERTION/SUICIDE
There is no test case, but there is debug instrumentation. We will investigate the scenario and track this change in MDEV-20126.

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