Skip to content

Percona Server for MySQL 8.0.15-5

Percona announces the release of Percona Server for MySQL 8.0.15-5 on March 15, 2019 (downloads are available here and from the Percona Software Repositories).

This release includes fixes to bugs found in previous releases of Percona Server for MySQL 8.0.

Starting from the release 8.0.15-5 , Percona Server for MySQL uses the upstream implementation of binary log encryption. The variable encrypt_binlog is removed and the related command line option --encrypt_binlog is not supported. It is important that you remove the encrypt_binlog variable from your configuration file before you attempt to upgrade from either another release in the Percona Server for MySQL 8.0 series or Percona Server for MySQL 5.7. Otherwise, a server boot error reports an unknown variable. The implemented binary log encryption is compatible with the old format: the binary log encrypted in a previous version of MySQL 8.0 series or Percona Server for MySQL are supported.

This release is based on MySQL 8.0.14 and 8.0.15. It includes all bug fixes in these releases. Percona Server for MySQL Percona Server for MySQL 8.0.14 was skipped.

Percona Server for MySQL 8.0.15-5 is now the current GA release in the 8.0 series. All of Percona’s software is open-source and free.

Percona Server for MySQL 8.0 includes all the features available in MySQL 8.0 Community Edition in addition to enterprise-grade features developed by Percona. For a list of highlighted features from both MySQL 8.0 and Percona Server for MySQL 8.0, please see the GA release announcement.

NOTE: If you are upgrading from 5.7 to 8.0, please ensure that you read the upgrade guide and the document Changed in Percona Server for MySQL 8.0.

Bugs Fixed

  • The audit log produced time stamps inconsistent with the ISO8601 standard. Bug fixed #226.

  • FLUSH commands written to the binary log could cause errors in case of replication. Bug fixed #1827 (upstream #88720).

  • When audit_plugin was enabled, the server could use a lot of memory when handling large queries. Bug fixed #5395.

  • The page cleaner could sleep for long time when the system clock was adjusted to an earlier point in time. Bug fixed #5221 (upstream #93708).

  • In some cases, the MyRocks storage engine could crash without triggering the crash recovery. Bug fixed #5366.

  • In some cases, when it failed to read from a file, InnoDB did not inform the name of the file in the related error message. Bug fixed #2455 (upstream #76020).

  • The ACCESS_DENIED field of the information_schema.user_statistics table was not updated correctly. Bugs fixed #3956, #4996.

  • MyRocks could crash while running START TRANSACTION WITH CONSISTENT SNAPSHOT if other transactions were in specific states. Bug fixed #4705.

  • In some cases, the server using the the MyRocks storage engine could crash when TTL (Time to Live) was defined on a table. Bug fixed #4911.

  • MyRocks incorrectly processed transactions in which multiple statements had to be rolled back. Bug fixed #5219.

  • A stack buffer overrun could happen if the redo log encryption with key rotation was enabled. Bug fixed #5305.

  • The TokuDB storage engine would assert on load when used with jemalloc 5.x. Bug fixed #5406.

Other bugs fixed: #4106, #4107, #4108, #4121, #4474, #4640, #5055, #5218, #5328, #5369.

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.

Last update: 2024-04-08