InnoDB: Undo tablespaces remained unencrypted after enabling undo tablespace encryption at startup. (Bug #29477795)

InnoDB: Problematic macros introduced with undo tablespace DDL support in MySQL 8.0.14 were revised. (Bug #29324132, Bug #94243)

InnoDB: Static thread local variables defined at the wrong scope were not released at thread exit. (Bug #29305186)

InnoDB: The performance_schema.data_locks LOCK_DATA column only showed the secondary index values of the locked record for a lock placed on a unique secondary index, which was not sufficient to ensure the uniqueness of identified records. The clustered index column values of the locked record are now appended. (Bug #29296645)

InnoDB: An incorrect count of transactions using a rollback segment for recovery of an XA transaction prevented an undo tablespace truncation operation from proceeding and left the purge thread busy checking for the undo tablespace to become empty. (Bug #29273194)

References: This issue is a regression of: Bug #29273194.

InnoDB: Invalid assertions were raised at startup after a failure to retrieve the space ID of a compressed file-per-table tablespace. The invalid assertion code was removed. (Bug #29221385, Bug #93760)

InnoDB: Optimized InnoDB internal temporary tables did not support in-place UPDATE operations, which caused the number of delete-marked records to increase continuously. The large number of delete-marked records could cause longer than expected query execution times. (Bug #29207450)

InnoDB: The std::sort function in the Variance-Aware Transaction Scheduling (VATS) algorithm was replaced by the std::stable_sortfunction to preserve the original FIFO order for transactions of equal weight. (Bug #29058967)

InnoDB: Write-ahead did not work as expected due to an incorrectly initialized variable.

Thanks to Yuhui Wang for the contribution. (Bug #29028838, Bug #93442)

InnoDB: The base column information for a generated column was not stored. (Bug #29021730)

InnoDB: An implicit lock check on secondary indexes needlessly compared columns using collation rules. (Bug #29010725)

InnoDB: Assertion code related to the innodb_flush_method O_DIRECT_NO_FSYNC setting was no longer valid due to a recent modification to that setting. Assertion code was revised. (Bug #29007731)

References: See also: Bug #27309336.

InnoDB: When starting the server with undo log encryption enabled, the master key for newly created undo tablespaces was generated without a server UUID. Undo tablespaces should use the DefaultMasterKey if the server UUID is not yet generated. (Bug #29006275)

InnoDB: Data dictionary code did not check for a returned data dictionary object, which could potentially cause the server to exit due to a null pointer access. (Bug #28977444, Bug #93362)

InnoDB: An undo tablespace file was left behind by a failed CREATE UNDO TABLESPACE operation. (Bug #28966457)

InnoDB: A CREATE UNDO TABLESPACE statement failed on Windows due to an invalid character in the file name. The failure resulted in a hang condition due to a missing OS_FILE_ON_ERROR_NO_EXIT attribute in the call that creates the undo tablespace file. (Bug #28955676)

InnoDB: Modifying the value of the innodb_undo_log_encrypt variable was not a blocking operation, which could lead to the modification being reverted by a background thread after the operation appeared to have been completed successfully. (Bug #28952870)

InnoDB: An invalid debug assertion was removed from the temptable::Handler::primary_key_is_clustered function. (Bug #28949332)

InnoDB: An ALTER TABLE ... EXCHANGE PARTITION operation did not properly update column table_id values in the data dictionary. (Bug #28927005)

InnoDB: Memory leaks discovered in the innochecksum utility were removed. (Bug #28917614, Bug #93164)

InnoDB: A DDL operation that followed a failed attempt to create an index on a virtual column resulted in an assertion failure. (Bug #28825718)

InnoDB: A performance regression was observed for partial update operations on compressed BLOBs less than or equal to 128KB in size. (Bug #28784301)

InnoDB: Running aggregated queries raised Valgrind warnings. (Bug #28711717)

InnoDB: A CHECK TABLE operation raised an assertion failure. A pointer to a local call stack variable was not set back to null before a function exit. (Bug #28525110)

InnoDB: DDL log functions were modified to handle ER_TOO_MANY_CONCURRENT_TRXS errors. (Bug #28523127, Bug #92071)

InnoDB: The purge thread failed to free LOB data pages. (Bug #28510599)

InnoDB: Some DDL log table transactions were not rolled back prior to DDL log recovery. (Bug #28494969)

InnoDB: A function invoked during SHOW CREATE TRIGGER processing that retrieves the table name did not perform the expected lowercase conversion. (Bug #28351038)

InnoDB: The INFORMATION_SCHEMA.INNODB_FOREIGN TYPE column reported incorrect values. (Bug #28315651, Bug #91577)

InnoDB: A Linux AIO handler function failed to check if completed I/O events succeeded. Thanks to Wei Zhao for the contribution. (Bug #27850600, Bug #90402)

InnoDB: An assertion failure was raised in a check that determines if a transaction holds an implicit lock on a secondary index. A transaction that does not change the columns of a secondary index that includes virtual columns could be incorrectly determined to hold an implicit lock. (Bug #27491839)

InnoDB: A function called by a CREATE TABLE thread attempted to access a table object after it was freed by a background thread.

Thanks to Yan Huang for the patch. (Bug #27373959, Bug #89126)

InnoDB: Two sessions concurrently executing an INSERT ... ON DUPLICATE KEY UPDATE operation generated a deadlock. During partial rollback of a tuple, another session could update it. The fix for this bug reverts fixes for Bug #11758237, Bug #17604730, and Bug #20040791. (Bug #25966845)

InnoDB: When the method used to access a joined table was const, InnoDB attempted to unlock the matching row multiple times. (Bug #20939184)

InnoDB: The INDEX_LENGTH value in INFORMATION_SCHEMA.TABLES was not updated when adding an index. (Bug #19811005)