Percona Server for MySQL 5.7.23-24 Is Now Available
Percona announces the release of Percona Server for MySQL 5.7.23-24 on November 12, 2018 (downloads are available here and from the Percona Software Repositories). This release merges changes of MySQL 5.7.23, including all the bug fixes in it. Percona Server for MySQL 5.7.23-24 is now the current GA release in the 5.7 series. All of Percona’s software is open-source and free.
This release introduces InnoDB encryption improvements and merges upstream MyRocks changes. Also, we’ve improved the usage of column families in MyRocks. The InnoDB encryption improvements are in Alpha quality and we don’t recommend that they are used in production.
New Features
- #4905: Upstream MyRocks changes have been merged
- #4976: InnoDB Undo Log Encryption has been implemented
- #4946: Add the
rocksdb_no_create_column_family
option to prevent the implicit creation of column families in MyRocks - #4556: InnoDB Redo Log Encryption has been implemented
- #3839: InnoDB Data Scrubbing has been implemented
- #3834: InnoDB Log Scrubbing has been implemented
Bugs Fixed
- #4723: PURGE CHANGED_PAGE_BITMAPS did not work when
innodb_data_home_dir
was used - #4937: rocksdb_update_cf_options was ignored when specified in my.cnf or on the command line
- #1107: The binlog could be corrupted when
tmpdir
got full - #4834: The encrypted system tablespace could have an empty uuid
Other bugs fixed
- #4106: “Assertion `log.getting_synced’ failed in
rocksdb::DBImpl::MarkLogsSynced(uint64_t, bool, const rocksdb::Status&)
“ - #4930: “main.percona_log_slow_innodb: Result content mismatch”
- #4811: “5.7 Merge and fixup for old DB-937 introduces possible regression”
- #4705: “crash on snapshot size check in RocksDB”
Find the release notes for Percona Server for MySQL 5.7.23-24 in our online documentation. Report bugs in the Jira bug tracker.
Comment (1)
Hi!
Just wondering that percona-server is still based on MySQL 5.7.23 instead of 5.7.24. Because you didn’t mention any CVE, does that mean any percona-server user is still affected by
– CVE-2018-3284
– CVE-2018-3282
– CVE-2018-3277
– CVE-2018-3251
– CVE-2018-3200
– CVE-2018-3174
…just to mention a few. And some of them allow for remote code execution.