Changes in MySQL 9.7.0 (2026-03-31, Early Access Release)

Note

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

• Audit Log Notes

• Authentication Notes

• Compilation Notes

• Component Notes

• Configuration Notes

• Replication with GTIDs

• InnoDB Notes

• JSON Notes

• Optimizer Notes

• Packaging Notes

• Functionality Added or Changed

• Bugs Fixed

Audit Log Notes

• Fixed an issue related to processing certain gzip files. The MySQL Server has been updated to relax the .gz header checks, allowing ordinary gzip files to be processed. Errors were returned similar to the following:

  Invalid audit log file content

  (Bug #38980223)

• Fixed an issue related to the audit_log_prune_seconds system variable. You can now set audit_log_prune_seconds. Checks have been added to ensure audit_log_prune_seconds does not exceed a certain threshold based on other system variable values, including log_offload.log_analytics_schedule and audit_log_rotate_on_time. (Bug #38941456)

• A new feature has been introduced that rotates the audit log file based on elapsed time, controlled by the new variable audit_log.rotate_on_time. (WL #17213)

• Audit Log now supports automatic recovery from invalid filter configurations, ensuring that the server can start even if an invalid filter is found in the table. With this update, if an invalid filter configuration is detected, it will be replaced in- memory at startup with a default filter that logs all events, preventing any loss of audit activity. This feature is controlled by the global variable audit_log.filter_recovery_mode (or audit_log_filter_recovery_mode for the Audit Log plugin), which allows users to choose from three recovery modes: LOG_ALL_IF_INVALID_FILTER_DETECTED, LOG_NOTHING_IF_INVALID_FILTER_DETECTED, and ABORT_IF_INVALID_FILTER_DETECTED. This enhancement provides greater flexibility and reliability in managing audit log configurations, reducing the risk of operational issues and ensuring that critical audit data is not missed.

  See audit_log.filter_recovery_mode and audit_log_filter_recovery_mode for more information. (WL #17179)

Authentication Notes

• Authentication now supports PBKDF2 storage format with Caching_sha2_password, providing enhanced security and flexibility. This update allows for the use of PBKDF2 with SHA512, enabling a smoother migration path from existing formats and ensuring even stronger security guarantees. With this change, users can switch to the new storage format without requiring client-side modifications, and administrators can enforce the preferred storage format for added security. Overall, this enhancement strengthens password protection and offers a more robust authentication experience.

  See Caching SHA-2 Pluggable Authentication for more information. (WL #17160)

Compilation Notes

• The included zlib library has been upgraded to version 1.3.2. (Bug #38987448)

Component Notes

• The following components, previously availabile only in MySQL Enterprise Edition, are now available in MySQL Community Edition:

  • Replication Applier Metrics Component

  • Group Replication Flow Control Statistics Component

  • Group Replication Resource Manager Component

  • Group Replication Primary Election Component

  (WL #17234, WL #17235, WL #17236, WL #17237)

• The Telemetry component, previously available only in MySQL Enterprise Edition, is now available in MySQL Community Edition.

  See Telemetry. (WL #17224)

Configuration Notes

• Microsoft Windows: On Windows, MySQL Configurator did not validate group names defined with --named-pipe-full-access-group.

  As of this release, an error is returned if the group does not exist. (Bug #38068986)

Replication with GTIDs

• A new variable, replica_allow_higher_version_source, has been introduced that lets you enable or disable replication from a higher version source into a lower version replica. (WL #17202)

InnoDB Notes

• InnoDB: Under certain circumstances, if the cgroups memory limit was set to a very high value, and --innodb-dedicated-server=ON, MySQL could fail to start. (Bug #37944614)

• MySQL Server now supports handling resource limitations set using the cpuset cgroup, providing a mechanism for assigning a set of CPUs to the application running in the cgroup. This update enables the server to adhere to the restrictions set by the cpuset-cpus cgroup controller, ensuring accurate calculation of logical CPUs available to the MySQL Server. With this enhancement, users can expect improved performance and efficient resource utilization, as the server can now correctly determine the number of logical CPUs according to cgroup restrictions. (WL #16851)

JSON Notes

• Using the monthname function within a JSON scope resulted in an assertion error. Errors were returned similar to the following:

  Assertion `mtime.time_type == MYSQL_TIMESTAMP_DATE in JSON

  (Bug #38980997)

• MySQL Community Server now supports DML operations on JSON Duality Views, enabling users to perform insert, update, and delete operations on these views. This enhancement expands the functionality of JSON Duality Views, which were previously limited to DDL operations in the Community Server edition. With this update, users can now fully leverage the capabilities of JSON Duality Views in MySQL Community Server, making it easier to manage and manipulate data in a flexible and efficient manner.

  See DML Operations on JSON Duality Views (MySQL Enterprise Edition) for more information. (WL #17246)

• MySQL now supports the use of auto-increment columns in DML operations with JSON duality views, allowing for more flexible and efficient data management. With this update, you can leverage auto-generated values for primary keys, enabling easier insertion of data into JSON duality views. The system automatically handles the generation of these values, streamlining the data insertion process and reducing the need for manual intervention. This enhancement provides a more seamless and intuitive experience for users working with JSON duality views, making it easier to manage and manipulate data in a variety of scenarios. (WL #17056)

Optimizer Notes

• TIMEDIFF() returned the wrong result if the first argument was DATETIME and the second argument was DATE. (Bug #38181443, WL #16895)

• TIMEDIFF() did not return NULL if unsupported values were used. (Bug #38179658, WL #16895)

• FROM_DAYS() did not handle out of range values, or values less than 366, consistently. (Bug #38177844, Bug #38177993, WL #16895)

• DAYNAME() did not return the day name if used in an arithmetic expression but returned the day number instead. (Bug #38177821, WL #16895)

• ADDDATE() returned an incorrect result if the first argument was year zero (0000). (Bug #38177766, WL #16895)

• CAST() of a year column returned the wrong result. (Bug #29616536, WL #16895)

• Under certain circumstances, INTERSECT could return an incorrect result. (Bug #117911, Bug #37804715)

Packaging Notes

• For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Server has been updated to version 3.5.0. For more information, see OpenSSL 3.5 Series Release Notes. (Bug #38867109, WL #17209)

Functionality Added or Changed

• The Hypergraph Optimizer is now available in MySQL Community Edition.

  It can be enabled in one of the following ways:

  • Session scope: SET optimizer_switch='hypergraph_optimizer=on|off'

  • Global scope: SET GLOBAL optimizer_switch='hypergraph_optimizer=on|off'

  • Persisted scope: SET PERSIST optimizer_switch='hypergraph_optimizer=on|off'

  • Server startup: mysqld --optimizer-switch='hypergraph_optimizer=on|off'

  • Per-statement hint: /*+ SET_VAR(optimizer_switch='hypergraph_optimizer=on|off') */

  (WL #17265)

Bugs Fixed

• Fixed an issue relating to Information Schema privileges. (Bug #35243416, Bug #37387633)