[MDEV-29766] Merge new release of InnoDB 5.7.40 to 10.3 Created: 2022-10-11  Updated: 2023-01-17  Resolved: 2022-10-11

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-29784 Q4 2022 release merge Closed
blocks MDEV-30422 Merge new release of InnoDB 5.7.41 to... Closed
is blocked by MDEV-29165 Merge new release of InnoDB 5.7.39 to... Closed

 Description   

MySQL 5.7.40 includes the following InnoDB changes:

Not applicable to MariaDB Server

Bug#34144951: InnoDB restore position crash when descent scan btree
This fixes a rare debug assertion in the function btr_cur_latch_leaves(). This code was refactored as part of MDEV-13542 in MariaDB Server 10.6.9. We do not run many stress tests on debug builds of MariaDB Server older than 10.6. This has no impact on non-debug builds.
Bug#32912868: dict_table_x_lock_indexes() can cause deadlock with concurrent purge operations
This was fixed in MDEV-22890.
BUG#34380370 truncate table not free mutex in some case
This should only affect crash-upgrades from 10.2.18 or earlier (before MDEV-13564). The code was completely removed from 10.4 in MDEV-13564. Crash-upgrades of 10.2 (or MySQL 5.7) to 10.3 or later should be prevented by MDEV-15912.

Because MariaDB Server 10.3 does not include a separate InnoDB version number (MDEV-16172), no code changes whatsoever will be necessary.


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