...
mysqld --initialize-insecure
systemctl start mysqld
echo "ALTER USER 'root'@'localhost' IDENTIFIED WITH 'mysql_native_password' BY '##########';" | mysql
...
InnoDB: Redo log records for modifications to undo tablespaces increased in size in MySQL 8.0 due to a change in undo tablespace ID values, which required additional bytes. The change in redo log record size caused a performance regression in workloads with heavy write I/O. To address this issue, the redo log format was modified to reduce redo log record size for modifications to undo tablespaces. (Bug #29536710)
Due to changes in MySQL 8.0.20 released by Oracle at the end of April 2020, Percona XtraBackup 8.0, up to version 8.0.11, is not compatible with MySQL version 8.0.20 or higher, or Percona products that are based on it: Percona Server for MySQL and Percona XtraDB Cluster.
6 月 8 2021
Percona XtraBackup 8.0.25-17.0 released
之前寫 MySQL 8.0.23 released 是 1 月的事,但 Percona XtraBackup 在兩個月後(3 月)才釋出 8.0.23-16.0;接著 MySQL 在 2021-04-20 釋出 8.0.24,2021-05-11 釋出 8.0.25 ,所以 Percona XtraBackup 的版本編號就直接跳上 8.0.25-17.0 了…
這個版本比較特別的是權限調整,需要額外賦予 performance_schema.keyring_component_status 這個 TABLE 的 SELECT 權限,如下圖標示處。

(參照:Percona XtraBackup – Documentation : Connection and Privileges Needed)
P.S. 在 Github 也可以看到紀錄: PXB-2490 xtrabackup privileges update (8.0)
分享此文:
By Joe Horn • Database 0 • Tags: MySQL, Percona XtraBackup