dataiotech Labs
dbaguidedbaguideDBAdataxtoolsdataopsphere
dbaguide.com
Home/Versions/mysql-8-4-lts
8.4 LTSLong Term Support (LTS) · Nisan 2024 (Aktif)8 min read

MySQL 8.4 LTS DBA Release Analysis: Deprecations, Native Password Sunset, and InnoDB Internals

The First Official LTS Release: Deprecated Subsystems, Security Hardening, and Migration Strategy

Senior DBA Evaluation Matrix
First Official LTS Release Cadence

Adopts a predictable 2-year LTS lifecycle backed by 5 years of stable enterprise support without breaking feature shifts.

⚠ Enterprise production clusters should standardize on 8.4 LTS rather than Innovation tracks.
mysql_native_password Disabled by Default

Legacy SHA-1 authentication is disabled by default, mandating modern caching_sha2_password protocols.

⚠ Legacy client drivers will fail to authenticate (ERROR 1045). Drivers must be upgraded prior to migration.
InnoDB Automatic Histogram Updates

Enhances execution plan stability via autonomous optimizer histogram tracking.

⚠ Reduces erratic execution plan regressions and incorrect index choices.

▸1. The New Release Model: LTS vs Innovation

With MySQL 8.4, Oracle split the server release train into two distinct tracks:

  1. 1LTS (Long Term Support): Published every 2 years with 5 years of premier maintenance and 3 years of extended support. No experimental syntax additions or breaking protocol changes are introduced. Designed strictly for mission-critical enterprise production.
  2. 2Innovation Releases: Published approximately every 3 months. Designed for early adopters to test bleeding-edge capabilities, with each release replaced by the next innovation milestone.

▸2. Top Production Migration Hazard: mysql_native_password

The single greatest source of post-migration outages in MySQL 8.4 is database authentication:

  • •mysql_native_password is now disabled by default.
  • •Outdated application drivers (older JDBC, PHP PDO, Python mysqlclient) will fail with ERROR 1045 (28000): Access denied for user.
sql
-- 1. Identify legacy accounts requiring plugin migration SELECT user, host, plugin FROM mysql.user WHERE plugin = 'mysql_native_password'; -- 2. Migrate accounts to modern caching_sha2_password ALTER USER 'app_user'@'%' IDENTIFIED WITH caching_sha2_password BY 'production_secure_pass_2026';

▸3. Removed Deprecated Server Variables

The following legacy variables are completely excised in MySQL 8.4; if present in your my.cnf / my.ini files, the server daemon will abort startup with fatal errors:

  • •innodb_log_file_size (Replaced by modern dynamic innodb_redo_log_capacity)
  • •innodb_log_files_in_group
  • •expire_logs_days (Replaced by binlog_expire_logs_seconds)
Back to Versions