What’s New in MySQL 8.3.0? Key Features and Changes Explained

MySQL 8.3.0 was released on Jan 16, 2024, introducing several new capabilities and deprecations.

Enterprise masking and data desensitization

Enterprise edition now can refresh masking dictionaries in the memory of replica (secondary) servers. Use masking_dictionaries_flush() for manual refresh or set the variable component_masking.dictionaries_flush_interval_seconds for scheduled refresh.

OpenTelemetry telemetry component

Enterprise edition supports the component_telemetry plugin to collect server metrics in OpenTelemetry format (Linux only).

Removed server options

The following options have been removed: --innodb and --skip-innodb (InnoDB is default since 5.6)

InnoDB memcached plugin

Various replication options and variables, including:

Replication changes

Using a non‑empty IGNORE_SERVER_IDS list is now prohibited when GTID‑based replication is enabled. The list must be cleared with CHANGE REPLICATION SOURCE TO IGNORE_SERVER_IDS = ().

GTID extended format

GTID now supports an extended format “UUID:<TAG>:NUMBER”. The <TAG> is any string set via SET gtid_next and persists for the session, allowing easier grouping of transactions.

Automated upgrade on Windows

MySQL Configurator can perform in‑place upgrades; for example, MySQL Server 8.3.0 can replace an existing 8.2.0 installation, updating and renaming the data directory automatically.

EXPLAIN JSON format version

A new system variable explain_json_format_version is added for EXPLAIN FORMAT=JSON. Value 1 is the default (legacy format); value 2 provides a path‑based format for future optimizer improvements.