InnoDB: InnoDB redo logging error messages now include the current LSN and redo log capacity information. A new warning code ER_IB_WRN_REDO_DISABLED_INFO is added which includes the current LSN. A new error code ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE_INFO is added to include the current log capacity and the current log capacity used. The MONITOR output has been enhanced to include redo log capacity details and current log capacity.

The warning ER_IB_WRN_REDO_DISABLED was removed, as was the error ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE. (Bug #37645185)

Fixed an issue related to bulk inserts. (Bug #38208188)

Fixed an issue relating to Common Table Expressions (CTE). (Bug #38573285)

Fixed an issue related to executing specific SQL queries. (Bug #38448700)

Fixed an issue relating to SHOW CREATE TABLE. (Bug #38298692)

Queries which used REGEXP took longer to execute as prepared statements than as direct queries. (Bug #114056, Bug #36326728)

For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Server has been updated to version 3.0.18. For more information, see OpenSSL 3.0 Series Release Notes. (Bug #38632932)

InnoDB: Under certain circumstances, when using the que_eval_sql interface, a race condition could occur. (Bug #118705, Bug #38310595)

Binary log purged before persisted binlog_expire_* options were loaded. (Bug #38554467)

When 2 of 6 instances in a geographically dispersed InnoDB Cluster lost connectivity, the primary server became unresponsive, causing the COMMIT and INSERT operations to become unresponsive as well. (Bug #38380392)

Fixed several issues relating to Thread Pool blocking connections from closing. (Bug #38170188, Bug #36782728, Bug #38549372)

GTID gaps were generated because of the replica- skip-errors option. (Bug #28590993)

If server was started on Windows platforms with --skip-grant-tables, privileges were not checked and remote connections were not permitted. As a result, the server might not start. (Bug #118805, Bug #38328780)