Percona Server

Percona Server is an open source, cross-platform and totally free software project that has been designed from the ground up as a drop-in replacement for the popular and widely used MySQL database engine/server.

While Percona Server is actually an enhanced version of the InnoDB storage engine designed for MariaDB and MySQL database servers, it includes full backward compatibility and it’s based on the Percona XtraDB Storage Engine project.

Features at a glance

Percona Server is scalable, as it handles more concurrent transactions on powerful servers, performant, as it uses a fast IO path, fast checksums, and improved internal cooperation, as well as flexible, with variable page size, configurable insert buffer, and better table and buffer pool management.

Percona Server is also extremely reliable and stable, featuring resilience to corrupted data and crash-safe transactional replication, manageable, with support for online backups, InnoDB table import/export functionality, fast recovery, and configurable data dictionary.

What can I do with Percona Server?

When using the Percona Server on your servers, your queries will run more consistently and a lot faster than with other similar products, it is possible to achieve higher uptime, as well as to save money on hosting power and unnecessary fees.

Furthermore, you will spend less time administering and optimizing your database server, and be able to build up state-of-the-art servers on powerful hardware. Additionally, guesswork is not required for troubleshooting and sharding can be avoided or delayed.

Under the hood and availability

The program is written entirely in the C++ programming language and it’s distributed as pre-built binary package for Debian/Ubuntu and Red Hat Enterprise Linux/Fedora operating systems, as well as source tarballs. At the moment, it has been successfully tested with both 32-bit and 64-bit instruction set architectures. A comprehensive manual is available on the project’s website.

What is new in this release:

• Based on MySQL 5.7.19, and including all the bug fixes in it, Percona Server for MySQL 5.7.19-17 is now the current GA release in the Percona Server for MySQL 5.7 series.

What is new in version 5.7.19-17:

• Based on MySQL 5.7.19, and including all the bug fixes in it, Percona Server for MySQL 5.7.19-17 is now the current GA release in the Percona Server for MySQL 5.7 series.

What is new in version 5.7.18-14:

• Based on MySQL 5.7.18, including all the bug fixes in it, Percona Server for MySQL 5.7.18-14 is the current GA release in the Percona Server for MySQL 5.7 series.

What is new in version 5.7.17-13:

• Based on MySQL 5.7.16, including all the bug fixes in it, Percona Server 5.7.16-10 is the current GA release in the Percona Server 5.7 series.

What is new in version 5.7.16-10:

• Based on MySQL 5.7.16, including all the bug fixes in it, Percona Server 5.7.16-10 is the current GA release in the Percona Server 5.7 series.

What is new in version 5.7.15-9:

• Based on MySQL 5.7.15, including all the bug fixes in it, Percona Server 5.7.15-9 is the current GA release in the Percona Server 5.7 series.

What is new in version 5.7.14-7:

• Based on MySQL 5.7.14, including all the bug fixes in it, Percona Server 5.7.14-7 is the current GA release in the Percona Server 5.7 series.

What is new in version 5.7.13-6:

• Based on MySQL 5.7.13.

What is new in version 5.7.12-5:

• Based on MySQL 5.7.10, including all the bug fixes in it, Percona Server 5.7.10-3 is the current GA release in the Percona Server 5.7 series.

What is new in version 5.7.10-3:

• Based on MySQL 5.7.10, including all the bug fixes in it, Percona Server 5.7.10-3 is the current GA release in the Percona Server 5.7 series.

What is new in version 5.6.27-75.0:

• Based on MySQL 5.6.27, including all the bug fixes in it, Percona Server 5.6.27-75.0 is the current GA release in the Percona Server 5.6 series.

What is new in version 5.6.26-74.0:

• Based on MySQL 5.6.26, including all the bug fixes in it, Percona Server 5.6.26-74.0 is the current GA release in the Percona Server 5.6 series

What is new in version 5.6.25-73.1:

• Based on MySQL 5.6.25, including all the bug fixes in it, Percona Server 5.6.25-73.1 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free - and this is the latest release of our enhanced, drop-in replacement for MySQL. Complete details of this release can be found in the 5.6.25-73.1 milestone on Launchpad.

What is new in version 5.6.24-72.2:

• Based on MySQL 5.6.24, including all the bug fixes in it, Percona Server 5.6.24-72.2 is the current GA release in the Percona Server 5.6 series.

What is new in version 5.6.22-72.0:

• Based on MySQL 5.6.22, including all the bug fixes in it, Percona Server 5.6.22-72.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free - and this is the latest release of our enhanced, drop-in replacement for MySQL.

What is new in version 5.6.22-71.0:

• Based on MySQL 5.6.22, including all the bug fixes in it, Percona Server 5.6.22-71.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free - and this is the latest release of our enhanced, drop-in replacement for MySQL.

What is new in version 5.6.21-70.1:

• Based on MySQL 5.6.21, including all the bug fixes in it, Percona Server 5.6.21-70.1 is the current GA release in the Percona Server 5.6 series.

What is new in version 5.6.21-70.0:

• Based on MySQL 5.6.21, including all the bug fixes in it, Percona Server 5.6.21-70.0 is the current GA release in the Percona Server 5.6 series.

What is new in version 5.5.35-33.0:

• Based on MySQL 5.5.35, including all the bug fixes in it, Percona Server 5.5.35-33.0 is now the current stable release in the 5.5 series.

What is new in version 5.1.73-14.11:

• Based on MySQL 5.1.73, including all the bug fixes in it, Percona Server 5.1.73-14.11 is now the current stable release in the 5.1 series.

What is new in version 5.6.15-63.0:

• Based on MySQL 5.6.15, including all the bug fixes in it, Percona Server 5.6.15-63.0 is the current GA release in the Percona Server 5.6 series.

What is new in version 5.5.34-32.0:

• This release is based on MySQL 5.5.34, including all the bug fixes in it, Percona Server 5.5.34-32.0 is now the current stable release in the 5.5 series.

What is new in version 5.1.72-14.10:

• Due to an incompatible upstream change that went in unnoticed, the page cleaner thread would attempt to replay any file operations it encountered. In most cases this were a no-op, but there were race conditions for certain DDL operations that would have resulted in server crash. Bug fixed #1217002.
• apt-get upgrade of Percona Server would fail in post-installation step if server failed to start. Bug fixed #1002500.
• Fixed the libssl.so.6 dependency issues in binary tarballs releases. Bug fixed #1172916.
• Percona Server could crash server could crash while accessing BLOB or TEXT columns in InnoDB tables if Support for Fake Changes was enabled. Bug fixed #1188168.
• A server could crash due to a race condition between a INNODB_CHANGED_PAGES query and a bitmap file delete by PURGE CHANGED_PAGE_BITMAP or directly on the file system. Bug fixed #1191580.

What is new in version 5.6.13-61.0:

• Based on MySQL 5.6.13, including all the bug fixes in it, Percona Server 5.6.13-61.0 is the first GA release in the Percona Server 5.6 series.

What is new in version 5.6.13-60.6 RC4:

• Based on MySQL 5.6.13, including all the bug fixes in it, Percona Server 5.6.13-60.6 is the fourth RC release in the Percona Server 5.6 series.

What is new in version 5.6.13-60.5 RC3:

• Percona is glad to announce the third Release Candidate of Percona Server 5.6.13-60.5 on August 29, 2013 (downloads are available here and from the Percona Software Repositories). Based on the recently released MySQL 5.6.13, including all the bug fixes in it, Percona Server 5.6.13-60.5 is the third RC release in the Percona Server 5.6 series. Percona Server is an enhanced, drop-in MySQL replacement. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.6.13-60.5 milestone at Launchpad.

What is new in version 5.5.33-31.1:

• Based on MySQL 5.5.33, including all the bug fixes in it, Percona Server 5.5.33-31.1 is now the current stable release in the 5.5 series.

What is new in version 5.1.71-14.9:

• Based on MySQL 5.1.71, this release will include all the bug fixes in it.

What is new in version 5.1.70-14.8:

• Bugs Fixed:
• Prevented a race condition that could lead to a server crash when querying the INFORMATION_SCHEMA.INNODB_BUFFER_PAGE table. Bug fixed #1072573.
• When an upgrade was performed between major versions (e.g. by uninstalling a 5.1 RPM and then installing a 5.5 one), mysql_install_db was still called on the existing data directory which lead to re-creation of the test database. Bug fixed #1169522.
• Fixed the upstream bug #68354 that could cause server to crash when performing update or join on Federated and MyISAM tables with one row, due to a bug in the Federated storage engine. Bug fixed #1182572.
• Other bug fixes: bug fixed #1191395.

What is new in version 5.5.32-31.0:

• New Features:
• Percona Server has implemented support for supplementary groups for PAM Authentication Plugin.
• Bugs Fixed:
• Prevented a race condition that could lead to a server crash when querying the INFORMATION_SCHEMA.INNODB_BUFFER_PAGE table. Bug fixed #1072573.
• Percona Server wouldn't start if the XtraDB changed page tracking was enabled and variable innodb_flush_method was set to ALL_O_DIRECT. Bug fixed #1131949.
• Fixed the upstream bug #68970 that, in Percona Server, would cause small tablespaces to expand too fast around 500KB tablespace size. Bug fixed #1169494.
• Query to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the middle of requested LSN range was missing. Bug fixed #1179974.

What is new in version 5.1.69-14.7:

• Bugs Fixed:
• In Ubuntu Precise libmysqlclient18 package was chosen from the distribution's repository instead of Percona's which could lead to package conflicts. Bug fixed #1174271.
• Fixed the RPM Percona-Server-shared-compat package naming issue that could lead to unresolved package dependencies when installing Percona Server 5.1. Bug fixed #893860.
• The log tracker thread was unaware of the situation when the oldest untracked log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the log parser or bad changed page data. Bug fixed #1108613.
• Percona Server wouldn't start if the XtraDB changed page tracking was enabled and variable innodb_flush_method was set to ALL_O_DIRECT. Bug fixed #1131949.
• Fixed the RPM package dependencies for different major versions of Percona Server. Bug fixed #1167109.
• Fixed the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts efficiently. This bug fix comes originally from MariaDB (see MDEV-3915). Bug fixed #1172090.
• OpenSSL libraries were not found in 32-bit builds due to a typo. Bug fixed #1175447.
• Query to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the middle of requested LSN range was missing. Bug fixed #1179974.
• Server would crash if an INNODB_CHANGED_PAGES query is issued that has an empty LSN range and thus does not need to read any bitmap files. Bug fixed #1184427.
• Incorrect schema definition for the User Statistics tables in INFORMATION_SCHEMA (CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS, THREAD_STATISTICS, and USER_STATISTICS) led to the maximum counter values being limited to 32-bit signed integers. Fixed so that these values can be 64-bit unsigned integers now. Bug fixed #714925.
• mysql_set_permission was failing on Debian due to missing libdbd-mysql-perl package. Fixed by adding the package dependency. Bug fixed #1003776.
• XtraDB changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed #1171699.
• Missing path separator between the directory and file name components in a bitmap file name could stop the server starting if the innodb_data_home_dir variable didn't have the path separator at the end. Bug fixed #1181887.
• A warning is now returned if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040.
• Fixed the upstream bug #69379 which caused MySQL clients to return bogus error number for host-not-found errors on Ubuntu 13.04. Bug fixed #1186690.
• Under very rare circumstances, deleting a zero-size bitmap file at the right moment would make server stop with an I/O error if changed page tracking is enabled. Bug fixed #1184517.
• The INNODB_CHANGED_PAGES table couldn't be queried if the log tracker wasn't running. Bug fixed #1185304.

What is new in version 5.6.11-60.3 RC:

• New Features:
• Percona Server has implemented Log Archiving for XtraDB. Currently this feature implementation is considered ALPHA quality.
• Complete list of the ported features can be seen in Percona Server 5.6.11-60.3 release notes.
• Bugs Fixed:
• Transaction objects are now allocated calling calloc() directly instead of using InnoDB heap allocation. This may improve write performance for high levels of concurrency. Bug fixed #1185686.
• Under very rare circumstances, deleting a zero-size bitmap file at the right moment would make server stop with an I/O error if changed page tracking is enabled. Bug fixed #1184517.
• Missing path separator between the directory and file name components in a bitmap file name could stop the server starting if the innodb_data_home_dir variable didn't have the path separator at the end. Bug fixed #1181887.
• Changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed #1171699.
• Incorrect schema definition for the User Statistics tables in INFORMATION_SCHEMA (CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS, THREAD_STATISTICS, and USER_STATISTICS) led to the maximum counter values being limited to 32-bit signed integers. Fixed so that these values can be 64-bit unsigned integers now. Bug fixed #714925.
• Server would crash if an INNODB_CHANGED_PAGES query is issued that has an empty LSN range and thus does not need to read any bitmap files. Bug fixed #1184427.
• Query to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the middle of requested LSN range was missing. Bug fixed #1179974.
• A warning is now returned if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040.
• The INNODB_CHANGED_PAGES table couldn't be queried if the log tracker wasn't running. Bug fixed #1185304.
• Fixed the upstream bug #68970 that, in Percona Server, would cause small tablespaces to expand too fast around 500KB tablespace size. Bug fixed #1169494.
• Fixed the RPM package dependencies issues. Bug fixed #1186831.
• Reduced the overhead from the Handle Corrupted Tables check as it was missing branch predictor annotations. Bug fixed #1176864.
• Other bug fixes: bug fixed #1184695, bug fixed #1184512, bug fixed #1183585, bug fixed #1178606, bug fixed #1177356, bug fixed #1160895, bug fixed #1182876, bug fixed #1180481, bug fixed #1163135, bug fixed #1157078, bug fixed #1182889, bug fixed #1133926, bug fixed #1165098, bug fixed #1182793, bug fixed #1157075, bug fixed #1183625, bug fixed #1155475, bug fixed #1157037, bug fixed #1182065, bug fixed #1182837, bug fixed #1177780, bug fixed #1154954.

What is new in version 5.5.31-30.3:

• New Features:
• Percona Server has ported the Atomic write support for Fusion-io devices patch from MariaDB. This feature adds atomic write support for directFS filesystem on Fusion-io devices. This feature implementation is considered BETA quality.
• Percona Server has introduced innodb_read_views_memory and innodb_descriptors_memory status variables in the Extended Show Engine InnoDB Status to improve InnoDB memory usage diagnostics.
• Bugs Fixed:
• Fix for bug #1131187 introduced a regression that could cause a memory leak if query cache was used together with InnoDB. Bug fixed #1170103.
• Fixed the RPM packaging regression that was introduced with the fix for bug #710799. This regression caused mysql schema to be missing after the clean RPM installation. Bug fixed #1174426.
• Fixed the Percona-Server-shared-55 and Percona-XtraDB-Cluster-shared RPM package dependences. Bug fixed #1050654.
• Fixed the upstream bug #68999 which caused compiling Percona Server to fail on CentOS 5 and Debian squeeze due to older OpenSSL version. Bug fixed #1183610.
• If a slave was running with its binary log enabled and then restarted with the binary log disabled, Crash-Resistant Replication could overwrite the relay log info log with an incorrect position. Bug fixed #1092593.
• Fixed the CVE-2012-5615 vulnerability. This vulnerability would allow remote attacker to detect what user accounts exist on the server. This bug fix comes originally from MariaDB (see MDEV-3909). Bug fixed #1171941.
• Fixed the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts efficiently. This bug fix comes originally from MariaDB (see MDEV-3915). Bug fixed #1172090.
• mysql_set_permission was failing on Debian due to missing libdbd-mysql-perl package. Fixed by adding the package dependency. Bug fixed #1003776.
• Rebuilding Debian source package would fail because dpatch and automake were missing from build-dep. Bug fixed #1023575 (Stephan Adig).
• Backported the fix for the upstream bug #65077 from the MySQL 5.6 version, which removed MyISAM internal temporary table mutex contention. Bug fixed #1179978.

What is new in version 5.5.30-30.2:

• New Features:
• Percona Server for MySQL has implemented priority connection scheduling for the Thread Pool. (Alexey Kopytov)
• Percona Server for MySQL will now be shipped with the libjemalloc library. Benchmark showing the impact of memory allocators on MySQL performance can be found in this blogpost. (Ignacio Nin)
• This release of Percona Server for MySQL has fixed a number of performance bugs. (Alexey Kopytov)
• Drop table performance feature has been removed and its controlling variable innodb_lazy_drop_table has been deprecated. Feature has been removed because the upstream DROP TABLE implementation has been improved. (Laurynas Biveinis)
• Bugs Fixed:
• Due to parse error in the percona-server.spec Percona Server rpm packages couldn't be built on RHEL 5 and CentOS 5. Bug fixed #1144777 (Ignacio Nin).
• When mysqldump was used with --innodb-optimize-keys option it produced invalid SQL for cases when there was an explicitly named foreign key constraint which implied an implicit secondary index with the same name. Fixed by detecting such cases and omitting the corresponding secondary keys from deferred key creation optimization. Bug fixed #1081016 (Alexey Kopytov).
• Percona Server for MySQL was built with YaSSL which could cause some of the programs that use it to crash. Fixed by building packages with OpenSSL support rather than the bundled YaSSL library. Bug fixed #1104977 (Ignacio Nin).
• Running the DDL statement while variable innodb_lazy_drop_table was enabled could cause assertion failure. Bugs fixed #1086227 and #1128848 (Laurynas Biveinis).
• Fixed yum dependencies that were causing conflicts in CentOS 6.3 during installation. Bugs fixed #1031427 and #1051874 (Ignacio Nin).
• The log tracker thread was unaware of the situation when the oldest untracked log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the log parser or bad changed page data. Bug fixed #1108613 (Laurynas Biveinis).
• Ported a fix from MariaDB for the upstream bug #63144. CREATE TABLE or CREATE TABLE IF NOT EXISTS statements on an existing table could wait on a metadata lock instead of failing or returning immediately if there is a transaction that executed a query which opened that table. Bug fixed #1127008 (Sergei Glushchenko).
• Fix for bug #1070856 introduced a regression in Percona Server for MySQL 5.5.28-29.3 which could cause a server to hang when binary log is enabled. Bug fixed #1162085 (Alexey Kopytov).
• Fixed upstream bug #49169 by avoiding the malloc call in the read_view_create_low() in most cases. This significantly improves InnoDB scalability on read-only workloads, especially when the default glibc memory allocator is used. Bug fixed #1131187 (Alexey Kopytov).
• Removed trx_list scan in read_view_open_now() which is another problem originally reported as upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov).
• In the event that a slave was disconnected from the master, under certain conditions, upon reconnect, it would report that it received a packet larger than the slave_max_allowed_packet variable. Bug fixed #1135097 (George Ormond Lorch III).
• Fixed the upstream bug #62578 which caused MySQL client to abort the connections on terminal resize. Bug fixed #925343 (Sergei Glushchenko).
• Percona Server for MySQL would re-create the test database when using rpm on server upgrade, even if the database was previously removed. Bug fixed #710799 (Alexey Bychko).
• Debian packages included the old version of innotop. Fixed by removing innotop and its InnoDBParser Perl package from source and Debian installation. Bug fixed #1032139 (Alexey Bychko).
• UDF/configure.ac was incompatible with automake 1.12. Bug fixed #1099387 (Alexey Bychko).
• Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch prediction. Bug fixed #1125248 (Alexey Kopytov).
• dialog.so used by the PAM Authentication Plugin couldn't be loaded with Perl and Python clients when plugin-dir option was set in the [client] section of the my.cnf. Bug fixed #1155859 (Sergei Glushchenko).
• Fixed the upstream bug #68845 which could unnecessarily increase contention on log_sys->mutex in write-intensive workloads. Bug fixed #1163439 (Alexey Kopytov).
• Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov).
• When mysqldump was used with --innodb-optimize-keys and --no-data options, all secondary key definitions would be lost. Bug fixed #989253 (Alexey Kopytov).
• Warning about the Percona Toolkit UDFs was omitted when installing from Percona's Debian repositories. Bug fixed #1015506 (Alexey Bychko).
• Percona Server for MySQL was missing help texts in the MySQL client because the help tables were missing. Bug fixed #1041981 (Alexey Bychko).
• Fixed the upstream bug #68197 that caused InnoDB to misclassify internal read operations as synchronous when they were actually asynchronous when Thread Pool feature was used. Bug fixed #1107539 (Sergei Glushchenko).
• Suboptimal code for User Statistics feature has been optimized to make sure no additional work is done when userstat is disabled. Bug fixed #1128066 (Alexey Kopytov).

What is new in version 5.1.68-14.5:

• This release contains no further bug fixes than what is included in the previous Percona Server release and MySQL 5.1.68.

What is new in version 5.6.10-60.2:

• New Features:
• Ported the Thread Pool patch from MariaDB. This feature enables the MySQL server to keep the top performance even with the increased number of client connections.
• Expanded Fast Index Creation has been ported from Percona Server for MySQL 5.5
• Handle Corrupted Tables feature has been ported from Percona Server for MySQL 5.5
• Bugs Fixed:
• Fixed the upstream #68116 that caused the MySQL server to crash with assertion error when InnoDB monitor with verbose lock info was used under heavy load. This bug is affecting only -debug builds. Bug fixed #1100178 (Laurynas Biveinis).