Percona XtraDB Cluster 8.0.32-24 (2023-04-18)¶
|Release date||April 18, 2023|
|Install instructions||Install Percona XtraDB Cluster|
Percona XtraDB Cluster (PXC) supports critical business applications in your public, private, or hybrid cloud environment. 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 is based on Percona Server for MySQL. Find a complete list of improvements and bug fixes in the Percona Server for MySQL 8.0.32-24 (2023-03-20) release notes.
Percona decided to revert the following MySQL bug fix:
The data and the GTIDs backed up by mysqldump were inconsistent when the options
--set-gtid-purged=ON were both used. It was because in between the transaction started by mysqldump and the fetching of GTID_EXECUTED, GTIDs on the server could have increased already. With this fixed, a FLUSH TABLES
WITH READ LOCK is performed before the fetching of
GTID_EXECUTED to ensure its value is consistent with the snapshot taken by mysqldump.
The Percona Server version of the
mysqldump utility, in some modes, can be used with MySQL Server. This utility provides a temporary workaround for the “additional RELOAD privilege” limitation introduced by Oracle MySQL Server 8.0.32.
For more information, see the Percona Performance Blog A Workaround for the “RELOAD/FLUSH_TABLES privilege required” Problem When Using Oracle mysqldump 8.0.32.
Improvements and bug fixes introduced by Oracle for MySQL 8.0.32 and included in Percona Server for MySQL are the following:
A replica can add a Generated Invisible Primary Keys(GIPK) to any InnoDB table. To achieve this behavior, the
GENERATEvalue is added as a possible value for the
CHANGE REPLICATION SOURCE TOstatement’s
REQUIRE_TABLE_PRIMARY_KEY_CHECK = GENERATEoption can be used on a per-channel basis.
sql_generate_invisible_primary_keyon the source is ignored by a replica because this variable is not replicated. This behavior is inherited from the previous releases.
An upgrade from 8.0.28 caused undetectable problems, such as server exit and corruption.
A fix for after an upgrade, all columns added with
ALGORITHM=INSTANTmaterialized and have
version=0for any new row inserted. Now, a column added with
ALGORITHM=INSTANTfails if the maximum possible size of a row exceeds the row size limit, so that all new rows with materialized
ALGORITHM=INSTANTcolumns are within row size limit. (Bug #34558510)
After a drop, adding a specific column using the INSTANT algorithm could cause a data error and a server exit. (Bug #34122122)
An online rebuild DDL no longer crashes after a column is added with
ALGORITHM=INSTANT. Thank you Qingda Hu for reporting this bug. (Bug #33788578, Bug #106279)
PXC-3936: State transfer with disabled SSL in
wsrep_provider_optionsoption crashed the Receiver and Donor nodes.
varswere not updated when 8.0 node joined the 5.7 cluster.
WSREPapplier threads failed to modify read-only schemas.
PXC-4162: When doing a rolling upgrade from 5.7 to 8.0,
pxc_strict_modeoption did not detect version mismatch.
Download product binaries, packages, and tarballs at Percona Product Downloads