Stable Release in branch 8.3
8.3.0
Released 14 Dec 2023
(2 years ago)
SoftwareMySQL
Version8.3
Status
End of life
Initial release8.3.0
14 Dec 2023
(2 years ago)
Latest release8.3.0
14 Dec 2023
(2 years ago)
End of
premier support
10 Apr 2024
(Ended 2 years ago)
End of
extended support
10 Apr 2024
(Ended 2 years ago)
Release noteshttps://dev.mysql.com/doc/relnotes/mysql/8.3/en/news-8-3-0.html
Source codehttps://github.com/mysql/mysql-server/tree/mysql-8.3.0
Documentationhttps://dev.mysql.com/doc/refman/8.3/en/
Downloadhttps://dev.mysql.com/downloads/mysql/
MySQL 8.3 ReleasesView full list

What Is New in MySQL 8.3

MySQL 8.3 introduces a set of incremental updates focused on stability and specific feature enhancements. This release primarily delivers bug fixes and performance improvements rather than major new functionality.

Category Description
New Features Limited to specific optimizer hints and the MEMBER attribute.
Functionality Added or Changed Changes to the mysql_native_password plugin and optimizer behavior.
Bugs Fixed A significant number of fixes across replication, optimizer, InnoDB, and other areas.
Deprecation and Removal Continued deprecation of the mysql_native_password plugin.

What are the key functional changes in MySQL 8.3?

The most notable functional change is the deprecation of the mysql_native_password authentication plugin. It's now deprecated and subject to removal in a future version. This change pushes users towards more secure authentication methods like caching_sha2_password.

For developers, a new optimizer hint, SET_VAR, has been introduced. This allows for setting session variables specifically for the execution of a single statement, giving more granular control over query optimization without affecting the entire session.

What performance and optimizer improvements were made?

This release includes several optimizer fixes that address specific edge cases in query execution. These fixes are aimed at preventing suboptimal query plans, which can significantly impact performance for complex queries.

In practice, these are the kind of under-the-hood tweaks that make a database more reliable. You might not notice them directly, but they help avoid those frustrating moments where a query suddenly becomes slow for no apparent reason.

How does MySQL 8.3 handle replication and clustering?

A number of bugs related to Group Replication and InnoDB Cluster have been resolved. The fixes target issues surrounding member expulsion, network timeouts, and transaction handling during certain failure scenarios.

This matters because it increases the stability and predictability of high-availability setups. For anyone running a clustered environment, these patches reduce the risk of unexpected cluster instability.

What about InnoDB and storage engine updates?

The InnoDB storage engine received its share of bug fixes, particularly concerning tablespace management and data dictionary operations. These are critical for maintaining data integrity, especially in high-write environments.

One specific fix prevents a potential crash during the renaming of a table that is placed in a non-default tablespace. It's a niche scenario, but one that could cause significant downtime if it occurred.

FAQ

Is MySQL 8.3 a major feature release?
No, it is not. MySQL 8.3 is an Innovation release focused primarily on bug fixes, performance improvements, and the deprecation of older features like the mysql_native_password plugin. It does not introduce a large number of new functionalities.

Should I upgrade to MySQL 8.3 immediately for performance gains?
Unless you are specifically affected by one of the bugs that was fixed, the performance gains might be subtle. The primary reason to upgrade would be to stay current with the latest stability patches and deprecation warnings.

What is the new SET_VAR optimizer hint?
It's a hint that allows you to set a session variable for the duration of a single statement. For example: SELECT /*+ SET_VAR(sort_buffer_size = 16M) */ id FROM t1 ORDER BY id;. This is useful for applying optimization settings without changing your global session context.

I still use mysql_native_password. What should I do?
You should begin planning a migration to a more secure authentication plugin, such as caching_sha2_password. While it still works in 8.3, it is officially deprecated and will be removed in a future version of MySQL.

Are there any changes for MySQL Shell in this release?
Yes, the release notes mention updates to MySQL Shell. These are typically updates for better compatibility with the server and bug fixes for the Shell's own functionality, rather than user-facing feature changes.

Releases In Branch 8.3

VersionRelease date
8.3.014 Dec 2023
(2 years ago)