MySQL 8.3 New Features and Removed Functionality
Version 8.3 of MySQL introduces tagged GTID replication, a selectable JSON EXPLAIN format version, enhanced thread‑pool plugin information, changes to binlog transaction dependency tracking and new CMake options, while removing several C API functions, the FLUSH HOSTS statement, and outdated replication flags.
MySQL 8.3 is the latest release of the widely used open‑source relational database, bringing new capabilities and deprecating some older features.
1 New Features
Tagged GTID Replication
MySQL 8.3 adds a tagged Global Transaction Identifier (GTID) format "UUID:TAG:NUMBER" that allows transactions to be grouped and easily identified. A new privilege TRANSACTION_GTID_TAG controls who can assign GTIDs.
JSON EXPLAIN Version Control
A server system variable explain_json_format_version lets users choose between two JSON output versions for EXPLAIN FORMAT=JSON , improving compatibility with future optimizer releases.
Thread‑Pool Plugin Enhancements
The thread‑pool plugin now provides additional tables and columns that expose detailed thread‑pool connection and state information, aiding performance analysis.
Other Notable Changes
The default value of the binlog_transaction_dependency_tracking variable is changed to WRITESET , indicating a gradual phase‑out of the previous setting.
A new CMake option WITH_LD allows users to specify the linker, and MySQL Enterprise Data Masking and De‑Identification receive enhancements.
Performance schema now includes richer thread‑pool connection details for tuning.
2 Removed Features
Several C API functions have been removed, including mysql_kill() , mysql_list_fields() , and others; users should adopt alternative methods.
The previously discouraged FLUSH HOSTS statement has been eliminated, with guidance to use newer mechanisms for clearing host caches.
Various replication and server options such as --slave-rows-search-algorithms and --log_bin_use_v1_events have been removed, encouraging more efficient modern practices.
Write‑set based logging is now limited to row‑based logging for conflict‑check writes, reflecting an improved approach to binary log transaction dependency tracking.
Users are encouraged to familiarize themselves with these changes to fully leverage MySQL 8.3 in database management tasks.
About SQLE
SQLE is a comprehensive SQL quality management platform covering development to production, supporting major open‑source, commercial, and domestic databases, and providing automated workflow capabilities for developers and operations.
GitHub: https://github.com/actiontech/sqle
Documentation: https://actiontech.github.io/sqle-docs/
Official site: https://opensource.actionsky.com/sqle/
Aikesheng Open Source Community
The Aikesheng Open Source Community provides stable, enterprise‑grade MySQL open‑source tools and services, releases a premium open‑source component each year (1024), and continuously operates and maintains them.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.