# Percona Server for MySQL 5.7.18-16 Is Now Available **URL:** \ **Category:** Percona Server for MySQL 5.7\ **Created:** [July 31, 2017, 3:56am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-7-18-16-is-now-available/5778 "2017-07-31T03:56:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![hrvojem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/hrvojem/32/6_2.png) [@hrvojem](https://forums.percona.com/u/hrvojem)\ **Post date:** [July 31, 2017, 3:56am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-7-18-16-is-now-available/5778/1 "2017-07-31T03:56:54Z")
Percona is glad to announce the GA release of Percona Server for MySQL 5.7.18-16 on July 28, 2017 (Downloads are available [here](http://www.percona.com/downloads/Percona-Server-5.7/Percona-Server-5.7.18-16/) and from the [Percona Software Repositories](https://www.percona.com/doc/percona-server/5.7/installation.html#using-percona-software-repositories)). Based on [MySQL 5.7.18](http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-18.html), including all the bug fixes in it, Percona Server for MySQL 5.7.18-16 is the current GA release in the Percona Server for MySQL 5.7 series. All of Percona’s software is open-source and free, and you can find all the release details in the [5.7.18-16 milestone at Launchpad](https://launchpad.net/percona-server/+milestone/5.7.18-16) Please note that RHEL 5, CentOS 5 and Ubuntu versions 12.04 and older are not supported in future releases of Percona Server and no further packages are added for these distributions. New Features: [LIST] [_]Percona Server for MySQL is now available on Debian 9 (stretch). The support only covers the amd64 architecture. [_]Percona Server for MySQL can now be built with the support of OpenSSL 1.1. [_]MyRocks storage engine has been merged into Percona Server. [_]TokuDB enables to kill a query that is awaiting an FT locktree lock. [_]TokuDB enables using the MySQL DEBUG\_SYNC facility within Percona FT. [/LIST] Bugs Fixed: [LIST] [_]Row counts in TokuDB could be lost intermittently after restarts. Bug fixed [#2](https://jira.percona.com/browse/TDB-2). [_]In TokuDB, two races in the fractal tree lock manager could significantly affect transactional throughput for some applications that used a small number of concurrent transactions. These races manifested as transactions unnecessarily waiting for an available lock. Bug fixed [#3](https://jira.percona.com/browse/TDB-3). [_]Percona FT could assert when opening a dictionary with no useful information to an error log. Bug fixed [#23](https://jira.percona.com/browse/TDB-23). [_]Percona FT could assert for various reasons deserializing nodes with no useful error output. Bug fixed [#24](https://jira.percona.com/browse/TDB-24). [_]It was not possible to build Percona Server on Debian 9 (stretch) due to issues with OpenSSL 1.1. Bug fixed [#1702903](https://bugs.launchpad.net/percona-server/+bug/1702903) (upstream [#83814](http://bugs.mysql.com/bug.php?id=83814)). [_]Packaging was using the dpkg --verify command which is not available on wheezy/precise. Bug fixed [#1694907](https://bugs.launchpad.net/percona-server/+bug/1694907). [_]Enabling and disabling the slow query log rotation spuriously added the version suffix to the next slow query log file name. Bug fixed [#1704056](https://bugs.launchpad.net/percona-server/+bug/1704056). [_]With two client connections to a server (debug server build), the server could crash after one of the clients set the global option userstat and flushed the client statistics (FLUSH CLIENT\_STATISTICS) and then both clients were closed. Bug fixed [#1661488](https://bugs.launchpad.net/percona-server/+bug/1661488). [_]Percona FT did not pass cmake flags on to snappy cmake. Bug fixed [#41](https://jira.percona.com/browse/TDB-41). The progress status for partitioned TokuDB table ALTERs was misleading. Bug fixed [#42](https://jira.percona.com/browse/TDB-42). [_]When a client application is connecting to the Aurora cluster end point using SSL (–ssl-verify-server-cert or --ssl-mode=VERIFY\_IDENTITY option), wildcard and SAN enabled SSL certificates were ignored. Note that the --ssl-verify-server-cert option is deprecated in Percona Server 5.7. Bug fixed [#1673656](https://bugs.launchpad.net/percona-server/+bug/1673656) (upstream [#68052](http://bugs.mysql.com/bug.php?id=68052)). [_]Killing a stored procedure execution could result in an assert failure on a debug server build. Bug fixed [#1689736](https://bugs.launchpad.net/percona-server/+bug/1689736) (upstream [#86260](http://bugs.mysql.com/bug.php?id=86260)). [_]The SET STATEMENT … FOR statement changed the global instead of the session value of a variable if the statement occurred immediately after the SET GLOBAL or SHOW GLOBAL STATUS command. Bug fixed [#1385352](https://bugs.launchpad.net/percona-server/+bug/1385352). [_]When running SHOW ENGINE INNODB STATUS, the Buffer pool size, bytes entry contained 0. BUg fixed [#1586262](https://bugs.launchpad.net/percona-server/+bug/1586262). [_]The synchronization between the LRU manager and page cleaner threads was not done at shutdown. Bug fixed [#1689552](https://bugs.launchpad.net/percona-server/+bug/1689552). [_]Spurious lock\_wait\_timeout\_thread wakeup in lock\_wait\_suspend\_thread() could occur. Bug fixed [#1704267](https://bugs.launchpad.net/percona-server/+bug/1704267) (upstream [#72123](http://bugs.mysql.com/bug.php?id=72123)). [/LIST] Other bugs fixed: [#1686603](https://bugs.launchpad.net/percona-server/+bug/1686603), [#6](https://jira.percona.com/browse/TDB-6), [#44](https://jira.percona.com/browse/TDB-44), [#65](https://jira.percona.com/browse/TDB-65), [#1160986](https://bugs.launchpad.net/percona-server/+bug/1160986), [#1686934](https://bugs.launchpad.net/percona-server/+bug/1686934), [#1688319](https://bugs.launchpad.net/percona-server/+bug/1688319), [#1689989](https://bugs.launchpad.net/percona-server/+bug/1689989), [#1690012](https://bugs.launchpad.net/percona-server/+bug/1690012), [#1691682](https://bugs.launchpad.net/percona-server/+bug/1691682), [#1697700](https://bugs.launchpad.net/percona-server/+bug/1697700), [#1699788](https://bugs.launchpad.net/percona-server/+bug/1699788), [#1121072](https://bugs.launchpad.net/percona-server/+bug/1121072), and [#1684601](https://bugs.launchpad.net/percona-server/+bug/1684601) (upstream [#86016](http://bugs.mysql.com/bug.php?id=86016)). The release notes for Percona Server for MySQL 5.7.18-16 are available in the [online documentation](https://www.percona.com/doc/percona-server/5.7/release-notes/Percona-Server-5.7.18-16.html). Please report any bugs on the [launchpad bug tracker](https://bugs.launchpad.net/percona-server/+filebug). Note Due to new package dependency, Ubuntu/Debian users should use apt-get dist-upgrade or apt-get install percona-server-server-5.7 to upgrade. ---
**Author:** ![Derek\_Perkins](https://avatars.discourse-cdn.com/v4/letter/d/67e7ee/32.png) [@Derek\_Perkins](https://forums.percona.com/u/Derek_Perkins)\ **Post date:** [August 12, 2017, 4:37pm UTC](https://forums.percona.com/t/percona-server-for-mysql-5-7-18-16-is-now-available/5778/2 "2017-08-12T16:37:16Z")
“MyRocks storage engine has been merged into Percona Server.” I can’t get the docker image to start with MyRocks support. It gives “unknown option ‘–rocksdb’” when I use the minimal rocksdb my.cnf. ---
**Author:** ![nuxwin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nuxwin/32/1172_2.png) [@nuxwin](https://forums.percona.com/u/nuxwin)\ **Post date:** [August 13, 2017, 5:36am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-7-18-16-is-now-available/5778/3 "2017-08-13T05:36:04Z")
Good morning, Could you clarify a bit about your choice to not provide any build for the i386 architecture (APT packages / Debian 9Stretch)? Thank you for your time.