Skip to content
Percona Software for MySQL Documentation
Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona XtraDB Cluster 8.4.11-11 (2026-10-05)

Percona XtraDB Cluster (PXC) supports critical business applications in both cloud and on-premises environments, including public, private, and hybrid setups. Our free, open source, enterprise-grade solution includes the high availability and security features your business requires to meet your customer expectations and business goals.

Percona XtraDB Cluster 8.4.11-11 is based on Percona Server for MySQL and includes all improvements and bug fixes available in the Percona Server for MySQL 8.4.11-11 (2026-08-20) release notes.

A note on MySQL 8.4.12

After a thorough review of the updates included in MySQL 8.4.12, Percona has decided not to release a corresponding Percona Server for MySQL 8.4.12. MySQL 8.4.12 is a Critical Security Patch Update (CSPU) — a targeted security release that Oracle can issue between quarterly Critical Patch Updates (CPUs) when needed. The fixes included in this CSPU do not affect Percona Server for MySQL.

Release highlights

Upgrade to 9.7

To upgrade from Percona XtraDB Cluster 8.4 to 9.7, use 9.7.2 or newer as the target version. Upgrading from 8.4.11 to 9.7.1 is not supported.

Percona Server for MySQL 8.4.11-11

Percona Server for MySQL 8.4.11-11 introduces the following new features and improvements:

  • Adds OpenID Connect (OIDC) authentication and authorization. Users can authenticate with Identity tokens issued by external Identity Providers (IDPs) instead of MySQL passwords. The OIDC plugin supports multiple IDPs, maps IDP groups to MySQL roles, supports proxy users based on group membership, and refreshes JSON Web Key Set (JWKS) signing keys at runtime. Find more information in OpenID Connect authentication and in Get started with OpenID Connect authentication.

  • Improves InnoDB performance for workloads limited by Least Recently Used (LRU) flush speed. The improvements reduce LRU list mutex contention, restore dedicated LRU manager threads, optimize LRU scanning, and allow single-page flushing to proceed while an LRU batch flush is running.

  • Improves InnoDB buffer pool initialization on NUMA-enabled systems by using multi-threaded memory allocation. The improvement reduces initialization time and can shorten server startup for instances with large buffer pools. Starting in 8.4.11, innodb_numa_interleave controls only interleaved NUMA allocations. Pre-faulting buffer pool pages on startup is controlled by innodb_buffer_pool_populate. Both default to ON, so default behavior matches 8.4.10. If you set innodb_numa_interleave=OFF to skip pre-faulting in 8.4.10, also set innodb_buffer_pool_populate=OFF in 8.4.11. See Defaults and tuning guidance for 8.4.

  • Improves InnoDB performance for highly concurrent range-select workloads by reducing BUF_BLOCK_MUTEX contention when multiple threads access the same buffer pool page. The improvement increases throughput for read workloads that repeatedly access the same hot pages.

  • Adds timestamps to the Group Communication System (GCS) debug trace file. The timestamps make large trace files easier to analyze and help correlate Group Replication communication events with other server activity.

MySQL 8.4.11

Improvements and bug fixes introduced by Oracle for MySQL 8.4.11 and included in Percona Server for MySQL are the following:

  • Fixed an issue that could cause an InnoDB deadlock during B-tree page merges while concurrent searches were running. (Bug #39129182)

  • Fixed an issue where stricter InnoDB row-size validation could reject or generate warnings for table definitions accepted by earlier MySQL LTS releases. (Bug #120323, Bug #39249507)

  • Fixed an issue that could produce incorrect values when adding an AUTO_INCREMENT column to an existing InnoDB table. (Bug #115136, Bug #37105825)

  • Fixed an issue that could return incorrect results when a scalar subquery and its outer query referenced the same Common Table Expression (CTE). (Bug #120403, Bug #39321676)

  • Fixed an issue that could prevent the server from starting on Oracle Linux 9 or Red Hat Enterprise Linux 9 when innodb_redo_log_encrypt=ON was configured. (Bug #39181231)

Find the complete list of bug fixes and changes in the MySQL 8.4.11 release notes .

Improvements

  • PXC-5106: When pxc_strict_mode is set to ENFORCING or MASTER, Percona XtraDB Cluster now also enables sql_require_primary_key globally, so tables without a primary key can no longer be created or altered. Previously, you could create such a table but could not run DML statements on it. While pxc_strict_mode is ENFORCING or MASTER, setting sql_require_primary_key to OFF returns an error. The server applies the setting at startup and whenever pxc_strict_mode changes to one of these modes. Existing connections keep their current session value, and new connections use the updated global value.

  • PXC-5208: Adds the repl.force_sst_after_inconsistency Galera provider option. When this option is enabled, a node removes the grastate.dat file on shutdown in two cases: when it is voted out of the cluster because of a data inconsistency, or when it fails to apply a write-set during Incremental State Transfer (IST) as a joiner. On the next start, the node performs a full State Snapshot Transfer (SST) instead of IST, which ensures a consistent dataset. The option is disabled by default and can be changed at runtime with wsrep_provider_options.

Bug fixes

  • PXC-5252: Fixed an issue where State Snapshot Transfer (SST) with the Clone plugin failed when the validate_password component enforced a strict password policy. The temporary SST user on the donor is no longer subject to password validation. For the Clone SST method, you can now set the sst-password-suffix option in the [sst] section to append characters that satisfy your password policy to the generated password.

  • PXC-5291: Fixed an issue where a user with the SET_ANY_DEFINER privilege but without the SUPER privilege could create a trigger while log_bin_trust_function_creators was disabled. Such statements are now rejected with the same error as in Percona Server for MySQL.

  • PXC-5292: Fixed an issue where a CREATE TRIGGER statement with a nonexistent DEFINER, run by a user with the SET_ANY_DEFINER privilege, could cause node inconsistency and eviction. The statement is now validated before it is replicated.

  • PXC-5305: Fixed an issue where a query could silently return incorrect results when an internal temporary table was converted from memory to an on-disk InnoDB table during execution. (MySQL Bug #116741)