Documentation Home
MySQL 8.0 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 4.4Mb
PDF (A4) - 4.4Mb


MySQL 8.0 Release Notes  /  Changes in MySQL 8.0.45 (2026-01-20, General Availability)

Changes in MySQL 8.0.45 (2026-01-20, General Availability)

Note

These release notes were created with the assistance of MySQL HeatWave GenAI.

InnoDB Notes

  • InnoDB: InnoDB redo logging error messages now include the current LSN and redo log capacity information, and the MONITOR output has been enhanced to display redo log capacity details. (Bug #37645185)

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

Optimizer Notes

  • 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)

Packaging Notes

  • 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)

Bugs Fixed

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

  • Binary log purged before persited 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)