InnoDB changes between mysql-9.5.0 and mysql-9.6.0

Note: We check the latest branch, because some bug fixes are for some reason being omitted from the earliest maintained branch (MySQL 8.4).

Not applicable to MariaDB Server

Bug#38132549: During recovery trx_sys->shards is mistakenly populated with processed transactions which can lead to failure
This is a follow-up to MySQL 8.0.27 Bug #33000142 INNODB CRASH LOCK0LOCK.CC: LOCK_GET_WAIT(OTHER_LOCK), which looks similar to MDEV-15326. The code bases have diverged a lot here; MDEV-22680 was our approach to reducing contention on trx_sys.mutex.
Bug#35659774 innodb_force_recovery rolls back prepared transactions
In MariaDB Server, the innodb_force_recovery should never break ACID properties. Basically, innodb_force_recovery=2 should only have an impact on garbage collection, and innodb_force_recovery>2 will make all InnoDB transactions read-only and disable any transaction commit. Hence, this bug never existed in MariaDB.
WL#16210 Remove unused upgrade code after WL#15924 (fixup)
This is apparently removing support for upgrading from MySQL 5.7 or earlier. We aim to support upgrade from any MariaDB version.
Bug#38235957: failure to DROP TABLE with an invalid CONSTRAINT
This appears to implement a subset of MDEV-11412.
Bug#33472935: dict_stats_analyze_index() may always discard optimal index-based access paths
This is a follow-up to an earlier change in MySQL 9.5.0. It seems possibly related to MDEV-10682.
Bug#35221441: FLUSH TABLE FOR EXPORT can lead to deadlock
This is something related to the MySQL clone functionality, which has not been implemented in MariaDB.
WL#16937 InnoDB : Container Aware Startup option
Loosely related to MDEV-19895, which we have not implemented yet.
2cdcc711a91 Post push fix to remove error log entry
This is removing some source code that was apparently not compiled into executable code. This code was never present in MariaDB.
Bug #38310595 when call que_eval_sql, may crash
This is related to lock wait handling in the InnoDB internal SQL interpreter. In MariaDB, the equivalent code could be invoked by the FULLTEXT INDEX subsystem. This problem had been fixed by MDEV-24671 and MDEV-30531 in MariaDB Server 10.6.
Bug#38430539: In some cases MDLs are released before Auto_releaser has run
This is related to the MySQL 8.0 Global Data Dictionary, which was not implemented in MariaDB.
Bug#38564593 Mysqld server crash from Btree_multi::bulk::Blob_inserter::close_blob at innobase/btr/btr0mtib.cc:3871
MariaDB does not include this bulk load interface.
Bug#13395168 IMPROVE DICT_SYS_GET_NEW_ROW_ID
MDEV-19506 removed this bottleneck altogether.
Bug#38208188: Bulk inserts into temporary tables with GIS indexes will inevitably cause crashes
This appears to be related to a bulk or parallel insert interface that has not been implemented in MariaDB.
Bug#36342348 - MVCC is broken for small partial update of blob
MariaDB only implements copy-on-write updates of InnoDB BLOB. The MySQL 8.0 tree-like BLOB has not been implemented in MariaDB.
Bug#37645185: Improve redo log related error log messages
InnoDB does not allow the redo log to be disabled (subject to be changed by MDEV-36301). The log overwrite messages were already improved in MDEV-29982.
Bug#38730874 pb2 mysql-trunk-cloud-asan bulk load failures
This fixes a bug in a MySQL specific bulk load interface.

Applicable to MariaDB Server

Bug#38492574: Unused variable fk_max_recusive_level
Filed as MDEV-38618.

Possibly applicable to MariaDB Server

WL#11249 - Support Foreign Key Cascading Operation in server
This is somewhat related to MDEV-22361 and MDEV-38243.
Bug#33788809: Prevent badly stale rec_per_key for query optimization
The addition of HA_STATUS_CONST_WHEN_UPDATED to Table_ref::fetch_number_of_rows() is something that could be applied to TABLE_LIST::fetch_number_of_rows() as a possible performance improvement. There are also some attempts to fix race conditions, which we have addressed in MDEV-10682, MDEV-35000 and MDEV-36227.
WL#16441 Bulk load into non-empty table (fixup)
This implements a bulk load option into a non-empty table by first copying the old contents of the table and then adding the data. MariaDB does not have a multi-threaded bulk load interface yet.