Percona Server for MySQL 8.0.15-6 Is Now Available

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

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 8.0.15-6 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.

New Features:

• The server part of MyRocks cross-engine consistent physical backups has been implemented by introducing rocksdb_disable_file_deletions and rocksdb_create_temporary_checkpoint session variables. These variables are intended to be used by backup tools. Prolonged use or other misuse can have serious side effects to the server instance.
• RocksDB WAL file information can now be seen in the performance_schema.log_status table.
• New Audit_log_buffer_size_overflow status variable has been implemented to track when an Audit Log Plugin entry was either dropped or written directly to the file due to its size being bigger than audit_log_buffer_size variable.

Bugs Fixed:

• TokuDB and MyRocks native partitioning would never release memory which could lead to a server crash. Bug fixed #5508.
• using TokuDB or MyRocks native partitioning and index_merge could lead to a server crash. Bugs fixed #5206, #5562.
• upgrade from Percona Server for MySQL 5.7.24-26 to 8.0.13-3 wasn’t working with encrypted undo tablespaces. Bug fixed #5223.
• Keyring Vault plugin couldn’t be initialized on Ubuntu Cosmic 17.10. Bug fixed #5453.
• rotated key encryption did not register encryption_key_id as a valid table option. Bug fixed #5482.
• INFORMATION_SCHEMA.GLOBAL_TEMPORARY_TABLES queries could crash if online ALTER TABLE was running in parallel. Bug fixed #5566.
• setting the log_slow_verbosity and enabling the slow_query_log could lead to a server crash. Bug fixed #4933.
• Compression dictionary operations were not handled under innodb-force-recovery. Bug fixed #5148.
• BLOB entries in the binary log could become corrupted in case when a database with Blackhole tables served as an intermediate binary log server in a replication chain. Bug fixed #5353.
• FLUSH CHANGED_PAGE_BITMAPS would leave gaps between the last written bitmap LSN and the InnoDB checkpoint LSN. Bug fixed #5446.
• XtraDB changed page tracking was missing pages changed by the in-place DDL. Bug fixed #5447.
• innodb_system tablespace information was missing from the INFORMATION_SCHEMA.innodb_tablespaces view. Bug fixed #5473.
• undo log tablespace encryption status is now available through INFORMATION_SCHEMA.innodb_tablespaces view. Bug fixed #5485 (upstream #94665).
• enabling temporay tablespace encryption didn’t mark the innodb_temporary tablespace with the encryption flag. Bug fixed #5490.
• server would crash during bootstrap if innodb_encrypt_tables was set to 1. Bug fixed #5492.
• fixed intermittent shutdown crashes that were happening if Thread Pool was enabled. Bug fixed #5510.
• compression dictionary INFORMATION_SCHEMA views were missing when datadir was upgraded from 8.0.13 to 8.0.15. Bug fixed #5529.
• innodb_encrypt_tables variable accepted FORCE option only as a string. Bug fixed #5538.
• ibd2sdi utility was missing from Debian/Ubuntu packages. Bug fixed #5549.
• Docker image is now ignoring password that is set in the configuration file when first initializing. Bug fixed #5573.
• long running ALTER TABLE ADD INDEX could cause a semaphore wait > 600 assertion. Bug fixed #3410 (upstream #82940).
• LOCK TABLES FOR BACKUP was blocking DML for RocksDB. Bug fixed #5583.

Other bugs fixed: #5537, #5243, #5371, #5475, #5484, #5512, #5514, #5523, #5528, #5536, #5550, #5554, #5570, #5578, #5441, #5442, #5456, #5462, #5487, #5489, #5501, #5520, and #5560.

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.

Find the release notes for Percona Server for MySQL 8.0.15-6 in our online documentation. Report bugs in the Jira bug tracker.

NOTE [2019-05-09]: Edit was made to add the missing bug fix descriptions.