[#MDEV-26867] Merge new release of InnoDB 5.7.36 to 10.2

[MDEV-26867] Merge new release of InnoDB 5.7.36 to 10.2 Created: 2021-10-20 Updated: 2022-01-18 Resolved: 2021-10-28
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
Fix Version/s:	10.2.41, 10.3.32, 10.4.22, 10.5.13, 10.6.5

Type:

Bug

Priority:

Blocker

Reporter:

Marko Mäkelä

Assignee:

Marko Mäkelä

Resolution:

Fixed

Votes:

Labels:

upstream

Issue Links:

Blocks
blocks	~~MDEV-27539~~	Merge new release of InnoDB 5.7.37 to...	Closed
is blocked by	~~MDEV-26205~~	Merge new release of InnoDB 5.7.35 to...	Closed
is blocked by	~~MDEV-26864~~	Race condition between transaction co...	Closed
is blocked by	~~MDEV-26865~~	fts_optimize_thread cannot keep up wi...	Closed
is blocked by	~~MDEV-26866~~	FOREIGN KEY…SET NULL corrupts an inde...	Closed
PartOf
is part of	~~MDEV-26898~~	2021 Q4 release merge	Closed

Description

MySQL 5.7.36 includes the following InnoDB changes:

Applicable to MariaDB Server

Bug#32771259: PAGE COMPRESSION OF INNODB TABLE IS IGNORED DURING RECOVERY PROCESS AND MIGHT NEVER SUCCESS WITH ENOSPC CRASH NEAR TO DISK-FULL
In MariaDB recovery, we recover the tablespace attributes based on the first page of the file, or the log written for them. This code was last touched in ~~MDEV-23199~~ and in the 10.6 optimization ~~MDEV-24626~~. The InnoDB redo log recovery does not depend on any data dictionary.
BUG#33181859: Followup for Bug 32800020 - the deadlocking continues
Thanks to us fixing ~~MDEV-12289~~ before the 10.2 GA release, MariaDB never broke the undo log compatibility with MySQL 5.6 or older MariaDB releases. All 128 rollback segments in the persistent data files continue to work just fine.

Generated at Thu Feb 08 09:48:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.