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

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.

blocks

MDEV-27539 Merge new release of InnoDB 5.7.37 to 10.2

is blocked by

MDEV-26205 Merge new release of InnoDB 5.7.35 to 10.2

MDEV-26864 Race condition between transaction commit and undo log truncation

MDEV-26865 fts_optimize_thread cannot keep up with workload

MDEV-26866 FOREIGN KEY…SET NULL corrupts an index on a virtual column

is part of

MDEV-26898 2021 Q4 release merge

(1 is part of)

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.