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.5-5 (2025-07-14)

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.

Release highlights

Percona XtraDB Cluster 8.4.5-5 is based on Percona Server for MySQL and includes all improvements and bug fixes available in the Percona Server for MySQL 8.4.5-5 (2025-05-29) release notes.

Percona XtraDB Cluster 8.4.5-5

Improves State Snapshot Transfer (SST) failure diagnostics. garbd now uses distinct exit codes to differentiate between donor exit, SST script failure, and garbd-initiated termination, making SST issues easier to identify and debug.

Percona Server for MySQL 8.4.5-5

  • Updates the C++ level of the KMPI library to enhance error handling capabilities.

  • Improves optimizer behavior by restoring correct handling of const tables in test_quick_select(). A MySQL Upstream refactor (commit 9a13c1c) removed the QEP_TAB dependency, causing get_quick_record_count() to no longer pass const table information. This could lead to suboptimal range scan boundaries. The applied patch resolves the issue by explicitly passing const_tables to test_quick_select(), ensuring consistent behavior with the pre-refactor logic.

MySQL 8.4.5

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

  • Fixed an issue where CHECK TABLE sometimes incorrectly reported that spatial indexes were corrupted. (Bug #37286473)

  • Fixed an issue in InnoDB redo log recovery to improve data safety after a crash. (Bug #37061960)

  • Fixed an issue where reading index_id values could lead to incorrect behavior with indexes. (Bug #36993445, Bug #37709706)

  • Fixed a bug related to the lower_case_table_names setting that caused inconsistent behavior with table names on different systems. (Bug #32288105)

  • Fixed a bug where mysqldump did not properly escape certain special characters in its output. (Bug #37540722, Bug #37709163)

  • The fprintf_string() function in mysqldump did not use the correct quote character for escaping strings. (Bug #37607195)

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

Bug fixes

  • PXC-3576: Percona XtraDB Cluster created role mappings using an upper-case database name when lower_case_table_names=1 was set.

  • PXC-4394: Improved error reporting for scenarios where Percona Xtrabackup, used during State Snapshot Transfer (SST), failed to report its version. These failures may be caused by missing libraries or a broken installation.

  • PXC-4399: Executing FLUSH TABLES on a table while writes were in progress caused the cluster node to stall.

  • PXC-4512: When RENAME TABLE was executed on a child table concurrently with INSERT/UPDATE on a parent table, a Metadata Lock (MDL) BF-BF conflict occured on the replica, causing two cluster nodes to enter NON-PRIMARY state.

  • PXC-4629: Creating a temporary table with CREATE TEMPORARY TABLE ... AS SELECT put the entire session into Transaction Ordered Index (TOI ) / Next Binary Operation (NBO) lock state, preventing any queries from being killed within that session.

  • PXC-4638: After performing State Snapshot Transfer (SST), the binlog.index file contents became inconsistent, causing the binlog_utils_udf plugin to fail when accessing the binlog file. Was fixed within PS-9777.

  • PXC-4652: Fixed a segmentation fault (SIGSEGV) on nodes with wsrep_applier_threads > 1 under high write activity.

  • PXC-4657: There was Metadata Lock (MDL) BF-BF conflict between two applier threads.

  • PXC-4684: An UPDATE query that referenced two tables but only modified one could cause an Metadata Lock (MDL) BF-BF conflict on other cluster nodes.

  • PXC-4664: Executing transactions with the same Global Transaction Identifier (GTID) on different nodes caused a node to exit.

  • PXC-4688: A regression in asynchronous replication caused the replica thread to stall when processing empty transactions.

  • PXC-3921: Node name can contain special characters.

  • PXC-4360: CLONE - percona_schema ‘mysql.pxc.sst.role@localhost’, a user cannot remove this privilege using REVOKE.