# Percona Server for MySQL 5.6.36-82.1 Is Now Available **URL:** \ **Category:** Percona Server for MySQL 5.6\ **Created:** [August 1, 2017, 10:00am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-6-36-82-1-is-now-available/5782 "2017-08-01T10:00:24Z")\ **Posts on this page:** 1\ **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:** [August 1, 2017, 10:00am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-6-36-82-1-is-now-available/5782/1 "2017-08-01T10:00:24Z")
Percona is glad to announce the release of Percona Server 5.6.36-82.1 on August 1, 2017 (Downloads are available [here](http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.36-82.1/) and from the [Percona Software Repositories](https://www.percona.com/doc/percona-server/5.6/installation.html)). Based on [MySQL 5.6.36](http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-36.html), including all the bug fixes in it, Percona Server 5.6.34-79.1 is the current GA release in the Percona Server 5.6 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the [5.6.36-82.1 milestone at Launchpad](https://launchpad.net/percona-server/+milestone/5.6.36-82.1). 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 can now be built with support of OpenSSL 1.1. [_]Percona Server is now available on Debian 9 (stretch). The support only covers the amd64 architecture. [_]TokuDB enables to kill a query that is awaiting an FT locktree lock. [/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). [_]TokuDB could assert when opening a dictionary with no useful information to error log. Bug fixed [#23](https://jira.percona.com/browse/TDB-23). [_]TokuDB could assert for various reasons deserializing nodes with no useful error output. Bug fixed [#24](https://jira.percona.com/browse/TDB-24). [_]Percona Server could crash when running a query over a partitioned table that uses an index to read a range of rows if this range was not covered by any existing partition. Bug fixed [#1657941](https://bugs.launchpad.net/percona-server/+bug/1657941) (upstream [#76418](http://bugs.mysql.com/bug.php?id=76418)). [_]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). [_]TokuDB 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 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. See also [Compatibility Matrix](https://www.percona.com/blog/?p=44673&preview=true#compatibility-matrix). 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)). [_]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)). [_]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). [\*]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). [/LIST] Other bugs fixed: [#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), [#1676740](https://bugs.launchpad.net/percona-server/+bug/1676740), [#1689989](https://bugs.launchpad.net/percona-server/+bug/1689989), [#1689998](https://bugs.launchpad.net/percona-server/+bug/1689998), [#1690012](https://bugs.launchpad.net/percona-server/+bug/1690012), [#1699788](https://bugs.launchpad.net/percona-server/+bug/1699788), and [#1684601](https://bugs.launchpad.net/percona-server/+bug/1684601) (upstream [#86016](http://bugs.mysql.com/bug.php?id=86016)).