Issues
- [ERROR] [FATAL] InnoDB: Apparent corruption of an index page to be written to data file. We intentionally crash the server to prevent corrupt data from ending up in data filesPXC-4138Resolved issue: PXC-4138
- InnoDB: Assertion failure in thread 140679940880128 in file btr0sea.cc line 1310 InnoDB: Failing assertion: index_id == index->idPXC-4104Resolved issue: PXC-4104
- Garbd IP is not visible in wsrep_incoming_addresses status variablePXC-3796Resolved issue: PXC-3796Kamil Holubicki
- Certification failure details are not logged with "cert.log_conflicts=yes"PXC-3746Resolved issue: PXC-3746Kamil Holubicki
- garbd doesn't correctly handle multiple incoming SST requests at the same timePXC-3691Resolved issue: PXC-3691Anton Matvienko
- Galera stops because of a replication error HA_ERR_NO_REFERENCED_ROWPXC-3656Resolved issue: PXC-3656
- When using keyring file plugin, keyring.backup can be left over without any error in the mysqld logPXC-3627Resolved issue: PXC-3627Marcelo Altmann
- "Encryption can't find master key" after SST when keyring_file is used if keyring.backup file existsPXC-3611Resolved issue: PXC-3611Marcelo Altmann
- Node stuck in aborting SSTPXC-3596Resolved issue: PXC-3596Marcelo Altmann
- LOCK=NONE usage is not supported in PXC-5.7 and abovePXC-3589Resolved issue: PXC-3589patrick.birch
- Correct Performance of SELECT in PXCPXC-3565Resolved issue: PXC-3565Zsolt Parragi
- PXC-5.7.32 upgrade is failing on debian/ubuntu distrosPXC-3539Resolved issue: PXC-3539Evgeniy Patlan
- Release tasks for PXC-5.7.32-31.47PXC-3527Resolved issue: PXC-3527Ramesh Sivaraman
13 of 13
