Percona XtraDB Cluster 8.0.28-19.1 (2022-07-19)¶
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.
Improvements and bug fixes introduced by Oracle for MySQL 8.0.28 and included in Percona Server for MySQL are the following:
CHARACTER SET latin1and
CHARACTER SET ucs2are deprecated and raise a warning to use
CHARACTER SETinstead. The shortcuts will be removed in a future version.
A stored function and a loadable function with the same name can share the same namespace. Add the schema name when invoking a stored function in the shared namespace. The server generates a warning when function names collide.
ALTER TABLE ... RENAME COLUMNoperations when using
The limit for
innodb_open_filesnow includes temporary tablespace files. The temporary tablespace files were not counted in the
innodb_open_filesin previous versions.
Find the full list of bug fixes and changes in the MySQL 8.0.28 Release Notes.
PXC-3923: When the
super_read_onlyoption was set, the
ANALYZE TABLEcommand removed the node from the cluster.
PXC-3388: Percona XtraDB Cluster stuck in a DESYNCED state after joiner was killed.
PXC-3609: The binary log status variables were updated when the binary log was disabled. Now the status variables are not registered when the binary log is disabled. (Thanks to Stofa Kenida for reporting this issue.)
PXC-3848: The cluster node exited when the
CURRENT_USER()function was used. (Thanks to Steffen Böhme for reporting this issue.)
PXC-3872: A user without system_user privilege was able to drop system users. (Thanks to user jackc for reporting this issue.)
PXC-3918: Galera Arbitrator (garbd) could not connect if the Percona XtraDB Cluster server used encrypted connections. The issue persisted even when the proper certificates were specified.
TRUNCATE TABLE Xand
INSERT INTO Xoptions when the foreign keys were disabled and violated caused the
HA_ERR_FOUND_DUPP_KEYerror on a slave node. (Thanks to Daniel Bartoníček for reporting this issue.)
wsrep_incoming_addressesstatus variable did not contain the garbd IP address.
To contribute to the documentation, review the Documentation Contribution Guide