Databases 12 min read

MySQL 8.0.19 Maintenance Release – New Features and Improvements

MySQL 8.0.19 introduces InnoDB ReplicaSet, Router enhancements, numerous SQL syntax additions, optimizer improvements, new Information Schema role views, security features, replication options, X Protocol compression, and a range of deprecations and bug fixes, providing a comprehensive update for database administrators and developers.

Aikesheng Open Source Community
Aikesheng Open Source Community
Aikesheng Open Source Community
MySQL 8.0.19 Maintenance Release – New Features and Improvements

InnoDB ReplicaSet

The new InnoDB ReplicaSet offers a full‑stack HA solution based on classic MySQL replication, using the AdminAPI in MySQL Shell to configure replication, data provisioning with CLONE, and automatic routing via MySQL Router.

Router

Router now supports InnoDB ReplicaSet metadata loading and caching, metadata schema upgrades, and a new –account startup option that allows reuse of existing server accounts.

SQL Enhancements

Added syntax includes ALTER TABLE…DROP / ALTER CONSTRAINT, SQL DROP CONSTRAINT, and ALTER CONSTRAINT clauses within ALTER TABLE. JSON Schema validation constraints now return row‑specific error messages. TIMESTAMP/DATETIME values can include time‑zone details, and LIMIT is supported in recursive CTEs. Table‑value constructors via VALUES() are now standardised, and INSERT…ON DUPLICATE KEY UPDATE can reference old/new rows.

Optimizer

Loose index scan for GROUP BY queries now removes the previous limitation on prefix range numbers, and Batch Key Access (BKA) is implemented for inner joins in the iterator executor.

Information Schema

New role‑related views (APPLICABLE_ROLES, ADMINISTRABLE_ROLE_AUTHORIZATIONS, ENABLED_ROLES, ROLE_TABLE_GRANTS, ROLE_COLUMN_GRANTS, ROLE_ROUTINE_GRANTS) expose SQL standard role information.

Security

Per‑user FAILED_LOGIN_ATTEMPTS and PASSWORD_LOCK_TIME counters enable temporary account lockout. The keyring plugin now supports storing opaque SECRET data up to 16 KB.

InnoDB

Support for sampling table data to build histograms and case‑insensitive handling of partition and sub‑partition names have been added.

Replication

Row‑based replication can be enforced, log‑slave‑updates can be disabled while preserving commit order, and TLS 1.3 support is added to client‑server connections with new MASTER_TLS_CIPHERSUITES options.

X Protocol

Connection compression, Zstandard compression, schema‑validated collection creation, and precise JSON schema error reporting have been introduced.

MTR Testsuite

Tests requiring MyISAM have been moved to separate files, allowing the suite to run without the MyISAM engine.

Other Improvements

Default –binary‑as‑hex is enabled for interactive mysql client, UDF API now allows charset specification, Sys Schema functions are replaced with Performance Schema equivalents, Windows mysql client gains the system command, admin sessions bypass max_connection limits, and error messages now include more context.

Deprecations and Removals

Display width for YEAR and UNSIGNED is deprecated, integer display width is removed from SHOW CREATE unless ZEROFILL is used, and the xplugin namespace is removed from X Protocol messages.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

databaseInnoDBmysqlReplicationSecurityX Protocol
Aikesheng Open Source Community
Written by

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.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.