Perconaannounces the release of Percona Server for MySQL 5.6.39-83.1 on February 13, 2018. Based on MySQL 5.6.39, including all the bug fixes in it, Percona Server for MySQL 5.6.39-83.1 is now the current stable release in the 5.6 series.
With innodb_large_prefix set to 1, Blackhole storage engine was incompatible with InnoDB table definitions, thus adding new indexes would cause replication errors on the slave. Fixed #1126 (upstream #53588).
Intermediary slave with Blackhole storage engine couldn’t record updates from master to its own binary log in case master has binlog_rows_query_log_events option enabled. Bug fixed #1119 (upstream #88057).
A build error on FreeBSD caused by fixing the bug #255 was present. Bug fixed #2284.
Server queries that contained JSON special characters and were logged by audit_log plugin in JSON format caused invalid output due to lack of escaping. Bug fixed #1115.
A memory leak fixed in PFS unit test. Bug fixed #1806 (upstream #89384).
A GCC 7 warning fix introduced regression in Percona Server for MySQL5.6.38-83.0 that lead to a wrong SQL query built to access the remote server when Federated storage engine was used. Bug fixed #1134.
Percona Server now uses Travis CI for additional tests. Bug fixed #3777.
This release also contains fixes for the following CVE issues: CVE-2018-2562,
CVE-2018-2573, CVE-2018-2583, CVE-2018-2590, CVE-2018-2591, CVE-2018-2612,
CVE-2018-2622, CVE-2018-2640, CVE-2018-2645, CVE-2018-2647, CVE-2018-2665,
CVE-2018-2668, CVE-2018-2696, CVE-2018-2703, CVE-2017-3737.
Percona fixed a memory leak in the PerconaFT library. Bug fixed #TDB-98.
A clang-format configuration was added to PerconaFT and TokuDB (bug fixed #TDB-104).
ProxySQL 1.4.5, released by ProxySQL, is now available for download in the Percona Repository along with an updated version of Percona’s proxysql-admin tool.
ProxySQL is a high-performance proxy, currently for MySQL and its forks (like Percona Server for MySQL and MariaDB). It acts as an intermediary for client requests seeking resources from the database. René Cannaò created ProxySQL for DBAs as a means of solving complex replication topology issues.
This release fixes the following bugs in ProxySQL Admin:
#PSQLADM-6: If the cluster node goes offline, the proxysql_node_monitor script now sets the node status as OFFLINE_HARD, and does not remove it from the ProxySQL database. Also, logging is consistent regardless of the cluster node online status.
#PSQLADM-30: Validation was added for the host priority file.
#PSQLADM-33: Added --proxysql-datadir option to run the proxysql-admin script with a custom ProxySQL data directory.
Also, BATS test suite was added for the proxysql-admin testing.
Fixed#PSQLADM-5: PXC mode specified with proxysql-admin with use of --mode parameter was not persistent.
Fixed#PSQLADM-8: ProxySQL High CPU load took place when mysqld was hanging.
ProxySQL is available under OpenSource license GPLv3.
From a Percona Live Santa Clara 2018 standpoint, beyond the tutorials getting picked and scheduled, the talks have also been picked and scheduled (so you were very likely getting acceptance emails from the Hubb.me system by Tuesday). The rejections have not gone out yet but will follow soon. I expect the schedule to go live either today (end of week) or early next week. Cheapest tickets end March 4, so don’t wait to register!
Probably the biggest news this week though? Transactions are coming to MongoDB 4.0. From the site, “MongoDB 4.0 will add support for multi-document transactions, making it the only database to combine the speed, flexibility, and power of the document model with ACID guarantees. Through snapshot isolation, transactions will provide a globally consistent view of data, and enforce all-or-nothing execution to maintain data integrity.”. You want to read the blog post, MongoDB Drops ACID (the title works if you’re an English native speaker, but maybe not quite if you aren’t). The summary diagram was a highlight for me because you can see the building blocks, plus future plans for MongoDB 4.2.
ProxySQL 1.4.6 – improvements and bug fixes, and you can upgrade straight to 1.4.6 (you don’t, for example, have to go to 1.4.5 then 1.4.6)
MariaDB Server 10.2.13 – updated InnoDB (from MySQL 5.7.21), Galera wsrep library, fixes for slow starts, and more
TOP 10 MySQL 8.0 features for developers – if you haven’t already tried the second release candidate, this might be a good reason to try it. From the document store to JSON enhancements, CTEs, window functions and more, I suggest taking a look at this great list.
From the just for fun department, MariaDB source visualisation with Gource. You see the source tree growing in the video, but as the commentary tells you, you don’t clean too much info from this. Would be nice to visualize how much the code-base has diverged?
SCALE16x – Pasadena, California, USA – March 8-11 2018