最新版的Percona Server有哪些优点

发布时间:2021-09-27 09:55:41 作者:iii
来源:亿速云 阅读:142

这篇文章主要讲解了“最新版的Percona Server有哪些优点”,文中的讲解内容简单清晰,易于学习与理解,下面请大家跟着小编的思路慢慢深入,一起来研究和学习“最新版的Percona Server有哪些优点”吧!

Percona Server 5.5.44-37.3 发布,此版本基于 MySQL 5.5.44,包括其所有 bug 修复,是当前 5.5 系列最新的稳定版本。此版本现已提供下载,也提供在 Percona Software Repositories。

Bugs 修复

Symlinks to libmysqlclient libraries were missing on CentOS 6. Bug fixed #1408500.

RHEL/CentOS 6.6 OpenSSL package (1.0.1e-30.el6_6.9), containing a fix for CVE-2015-4000, changed the DH key sizes to a minimum of 768 bits. This caused an issue for MySQL as it uses 512 bit keys. Fixed by backporting an upstream 5.7 fix that increases the key size to 2048 bits. Bug fixed #1462856 (upstream #77275).

innochecksum would fail to check tablespaces in compressed format. The fix for this bug has been ported from Facebook MySQL 5.1 patch. Bug fixed #1100652 (upstream #66779).

Issuing SHOW BINLOG EVENTS with an invalid starting binlog position would cause a potentially misleading message in the server error log. Bug fixed #1409652 (upstream #75480).

While using max_slowlog_size, the slow query log was rotated every time slow query log was enabled, not really checking if the current slow log is indeed bigger than max_slowlog_size or not. Bug fixed #1416582.

If query_response_time_range_base variable was set as a command line option or in a configuration file, its value would not take effect until the first flush was made. Bug fixed #1453277 (Preston Bennes).

Prepared XA transactions with update undo logs were not properly recovered. Bug fixed #1468301.

Variable log_slow_sp_statements now supports skipping the logging of stored procedures into the slow log entirely with new OFF_NO_CALLS option. Bug fixed #1432846.

其他 bug 修复: #1380895 (upstream #72322)。更多改进内容请看发行说明。

Percona Server 5.6.25-73.0 发布,此版本现已提供在 Percona web site 和 Software Repositories。

此版本基于 MySQL 5.6.25,包括其所有 bug 修复,是当前 5.6 系列最新的 GA 版本。

新特性

Percona Server 实现了对 PROXY 协议的支持。

Bugs 修复

Symlinks to libmysqlclient libraries were missing on CentOS 6. Bug fixed #1408500.

RHEL/CentOS 6.6 OpenSSL package (1.0.1e-30.el6_6.9), containing a fix for CVE-2015-4000, changed the DH key sizes to a minimum of 768 bits. This caused an issue for MySQL as it uses 512 bit keys. Fixed by backporting an upstream 5.7 fix that increases the key size to 2048 bits. Bug fixed #1462856 (upstream #77275).

Some compressed InnoDB data pages could be mistakenly considered corrupted, crashing the server. Bug fixed #1467760 (upstream #73689) Justin Tolmer.

innochecksum would fail to check tablespaces in compressed format. The fix for this bug has been ported from Facebook MySQL 5.6 patch. Bug fixed #1100652 (upstream #66779).

Using concurrent REPLACE, LOAD DATA REPLACE or INSERT ON DUPLICATE KEY UPDATE statements in the READ COMMITTED isolation level or with the innodb_locks_unsafe_for_binlog option enabled could lead to a unique-key constraint violation. Bug fixed #1308016 (upstream #76927).

Issuing SHOW BINLOG EVENTS with an invalid starting binlog position would cause a potentially misleading message in the server error log. Bug fixed #1409652 (upstream #75480).

While using max_slowlog_size, the slow query log was rotated every time slow query log was enabled, not really checking if the current slow log is indeed bigger than max_slowlog_size or not. Bug fixed #1416582.

Fixed possible server assertions when Backup Locks are used. Bug fixed #1432494.

If query_response_time_range_base variable was set as a command line option or in a configuration file, its value would not take effect until the first flush was made. Bug fixed #1453277 (Preston Bennes).

mysqld_safe script is now searching for libjemalloc.so.1 library, needed by TokuDB, in the basedir directory as well. Bug fixed #1462338.

Prepared XA transactions could cause a debug assertion failure during the shutdown. Bug fixed #1468326.

Variable log_slow_sp_statements now supports skipping the logging of stored procedures into the slow log entirely with new OFF_NO_CALLS option. Bug fixed #1432846.

TokuDB HotBackup library is now automatically loaded with mysqld_safe script. Bug fixed #1467443.

其他 bug 修复 #1457113, #1380895, and #1413836。更多改进内容请看发行说明。

Percona 为 MySQL 数据库服务器进行了改进,在功能和性能上较 MySQL 有着很显著的提升。该版本提升了在高负载情况下的 InnoDB 的性能、为 DBA 提供一些非常有用的性能诊断工具;另外有更多的参数和命令来控制服务器行为。

Percona Server 只包含 MySQL 的服务器版,并没有提供相应对 MySQL 的 Connector 和 GUI 工具进行改进。

Percona Server 使用了一些 google-mysql-tools, Proven Scaling, Open Query 对 MySQL 进行改造。

感谢各位的阅读,以上就是“最新版的Percona Server有哪些优点”的内容了,经过本文的学习后,相信大家对最新版的Percona Server有哪些优点这一问题有了更深刻的体会,具体使用情况还需要大家实践验证。这里是亿速云,小编将为大家推送更多相关知识点的文章,欢迎关注!

推荐阅读:
  1. Percona XtraDB Cluster规划实施
  2. Percona Server、MariaDB、MYSQL应该如何选择

免责声明:本站发布的内容(图片、视频和文字)以原创、转载和分享为主,文章观点不代表本网站立场,如果涉及侵权请联系站长邮箱:is@yisu.com进行举报,并提供相关证据,一经查实,将立刻删除涉嫌侵权内容。

percona server

上一篇:java中如何使用mat分析java堆

下一篇:ServletContext.getRealPath()输入参数要以”/”开头的示例分析

相关阅读

您好,登录后才能下订单哦!

密码登录
登录注册
其他方式登录
点击 登录注册 即表示同意《亿速云用户服务条款》