MY
MySQL 26.7.0
Get release alerts
9.7.1β26.7.0SecurityFeatureBreakingBug fixPerformanceDeprecation
β¦ Editor's summary
MySQL 26.7.0 introduces MySQL's new calendar-based versioning scheme (YY.M.P), replacing the previous sequential version numbering. The release delivers security enhancements, performance and InnoDB improvements, new Community Edition capabilities, replication changes, and numerous bug fixes. It also introduces several deprecations that administrators should review before future upgrades.
β Security impact
- Introduces additional post-quantum cryptography (PQC) capabilities for TLS connections, including support across administrative, replication, and MySQL X Plugin connections.
- Updates the bundled libfido2 library to version 1.17.0.
- Includes security-related improvements to authentication and encrypted connection capabilities.
What's new
- Introduces the new calendar-based versioning model, replacing the previous sequential version numbering used by releases such as MySQL 9.7.
- Adds post-quantum cryptography capabilities for TLS connections, including administrative, replication, and MySQL X Plugin connections.
- Makes the MySQL Thread Pool plugin available in MySQL Community Edition.
- Changes the default
thread_pool_max_unused_threadsvalue from 2 to 32. - Adds the
--extended-insert-multilineoption tomysqldump. - Improves InnoDB performance and stability, including reduced contention during index creation and table truncation.
- Updates MySQL Clone behavior to support the new calendar-based versioning model.
- Improves JSON relational duality views and fixes multiple JSON processing and validation issues.
- Includes numerous optimizer fixes addressing crashes, incorrect query results, JOIN processing, CTE handling, ROLLUP queries, and aggregation.
- Includes multiple replication, Performance Schema, Audit Log, X Plugin, and InnoDB fixes.
group_replication_communication_stackis deprecated and scheduled for removal in a future release.group_replication_ip_allowlistis deprecated and scheduled for removal in a future release.
This release introduces a major version-numbering transition. Organizations should review version-detection scripts, deployment automation, monitoring tools, backup processes, and application compatibility before upgrading.
More from MySQL
Latest in Databases
π¬ Comments (0)
Share any installation issues, compatibility changes, or fixes you noticed.