MySQL 5.7.15 发布,新增 InnoDB 和 CMake 选项

MySQL 5.7.15 发布了。更新如下:

安全事项:

The validate_password plugin now supports the capability of rejecting passwords that match the current session user name, either forward or in reverse. To enable control over this capability, the plugin exposes a validate_password_check_user_name system variable. By default, this variable is disabled; the default will change to enabled in MySQL 8.0. For more information, see Password Validation Plugin Options and Variables.
功能增加或改变:

InnoDB: A new dynamic configuration option, innodb_deadlock_detect, can be used to disable deadlock detection. On high concurrency systems, deadlock detection can cause a slowdown when numerous threads wait for the same lock. At times, it may be more efficient to disable deadlock detection and rely on the innodb_lock_wait_timeout setting for transaction rollback when a deadlock occurs. (Bug #23477773)
The systemd support script for the unit file (mysqld_pre_systemd) now assists in creating the error log file only if its location matches the pattern /var/log/mysql*.log. In other cases, the error log directory must be writable or the error log must be present and writable for the user running themysqld process. Also, mysqld_pre_systemd now avoids creating insecure temporary files. (Bug #24516262)
The CMake WITH_LZ4 option has been added to control which LZ4 library is used during compilation. By default WITH_LZ4 is set to bundled, so the library provided with MySQL is used. Setting WITH_LZ4 to system uses the LZ4 library from the operating system. (Bug #23607230)
Bugs 修复:

InnoDB: An ALTER TABLE ... ENCRYPTION=‘Y‘, ALGORITHM=COPY operation on a table residing in the system tablespace raised an assertion. (Bug #24381804)
InnoDB: Creating an encrypted table on a Fusion-io disk with an innodb_flush_method setting of O_DIRECT caused a fatal error. (Bug #24329079, Bug #82073)
InnoDB: An operation that dropped and created a full-text search table raised an assertion. (Bug #24315031)
InnoDB: Accessing full-text search auxiliary tables while dropping the indexed table raised an assertion. (Bug #24009272)
InnoDB: An online DDL operation on a table with indexed BLOB columns raised an assertion during logging of table modifications. (Bug #23760086)
InnoDB: In some cases, code that locates a buffer pool chunk corresponding to given pointer returned the wrong chunk.Thanks to Alexey Kopytov for the patch. (Bug #23631471, Bug #79378)
Replication: The addition of the transaction-write-set-extraction=XXH64 option uses xxHash symbols from liblz4. Although the xxHash symbols are exported by liblz4, the header file is not part of the API, so compilation failed when building with WITH_LZ4=system. The fix ensures that xxHash is built separately from liblz4 so that it is available both when using the system and bundled LZ4 libraries. (Bug #82426, Bug #24399819)References: See also: Bug #23607230.
Replication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new connection for log2 without freeing the connection used forlog1. Thanks to Laurynas Biveinis for the contribution. (Bug #81675, Bug #23540182)
Replication: The MTR binary log test suite failed to clean up copied files. Thanks to Daniel Black for the contribution. (Bug #80881, Bug #23016254)
Replication: With binlog_row_image=FULL, when updating single tables temporary tables were unnecessarily being used. The fix ensures single table update follows the same pattern as multi-table update. (Bug #79867, Bug #22510353)
mysqld_safe attempted to read my.cnf in the data directory, although that is no longer a standard option file location. (Bug #24482156)
For mysqld_safe, the argument to --malloc-lib now must be one of the directories /usr/lib, /usr/lib64, /usr/lib/i386-linux-gnu, or/usr/lib/x86_64-linux-gnu. In addition, the --mysqld and --mysqld-version options can be used only on the command line and not in an option file. (Bug #24464380)
It was possible to write log files ending with .ini or .cnf that later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with .ini or .cnf. (Bug #24388753)
Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug #24388746)
The client library failed to build on Solaris using the Cstd library. (Bug #24353920)
If the basedir system variable was set at server startup from the command line or option file, the value was not normalized (on Windows, / was not replaced with /). (Bug #23747899, Bug #82125)
kevent statement timer subsystem deinitialization was revised to avoid a mysqld hang during shutdown on OS X 10.12. (Bug #23744004, Bug #82097)
For accounts for which multiple GRANT statements applied, mysqlpump could fail to dump them all. (Bug #23721446)
The MYSQL_ADD_PLUGIN macro had a spelling error that caused MYSQL_SERVER not to be defined. (Bug #23508762, Bug #81666)
In-place ALTER TABLE operations which when executed separately caused no table rebuild could when combined into a single statement result in a table rebuild. (Bug #23475211, Bug #81587)
For keyring plugins, the data access layer is now created only as necessary, not once per operation, which improves keyring performance. (Bug #23337926)
A blank server name in CREATE SERVER statements produced a server exit rather than an error. (Bug #23295288)
The optimizer failed to check a function return value for an area calculation, leading to a server exit. (Bug #23280059)
The server could fail to free memory allocated for execution of queries that used generated columns. (Bug #23205454)References: This issue is a regression of: Bug #22392268.
mysqlpump output for triggers that contained multiple statements in the trigger body failed to load correctly. (Bug #23072245)
Queries that satisfied the following conditions could return different results than in MySQL 5.6: 1) A subquery appeared in the select list; 2) The subquery contained a WHERE condition that referenced a value in the outer query; 3) The outer query contained a GROUP BY that required creation of a temporary table. (Bug #23049975)
Passwords that were rejected by the validate_password plugin were written by the server to the error log as cleartext. (Bug #22922023)
A prepared statement that used a parameter in the select list of a derived table that was part of a join could cause a server exit. (Bug #22392374, Bug #24380263)
MEDIUMINT columns used in operations with long integer values could result in buffer overflow. (Bug #19984392)
A spurious ER_NO_SUCH_TABLE error could occur when attempting to execute a prepared CREATE TABLE ... SELECT statement that used a temporary table in the FROM clause and called a stored function. The same error could occur for a nonprepared version of the statement if used in a stored procedure when the procedure was re-executed. (Bug #16672723, Bug #68972)
EINTR handling in the client library has been fixed so that interrupted read and write calls are retried. Previously, EINTR was ignored. (Bug #82019, Bug #23703570)
查看其它bug更新及完整更新列表,请点击mysql/5.7/en/news-5-7-15.html

下载地址:http://dev.mysql.com/downloads/mysql/

时间: 2024-10-12 13:20:50

MySQL 5.7.15 发布,新增 InnoDB 和 CMake 选项的相关文章

MySQL 5.7.15 发布,新增 InnoDB 配置选项

MySQL 5.7.15 发布了.更新如下: 安全事项: The validate_password plugin now supports the capability of rejecting passwords that match the current session user name, either forward or in reverse. To enable control over this capability, the plugin exposes a validate

MySQL 5.6 Reference Manual-14.6 InnoDB Table Management

14.6 InnoDB Table Management 14.6.1 Creating InnoDB Tables 14.6.2 Moving or Copying InnoDB Tables to Another Machine 14.6.3 Grouping DML Operations with Transactions 14.6.4 Converting Tables from MyISAM to InnoDB 14.6.5 AUTO_INCREMENT Handling in Inn

secilog 1.15 发布 增加了搜索保存数据库采集web日志报表等。

日志分析软件 secilog 1.15发布,增加了搜索保存数据库采集web日志报表等.上篇文章1.13,有兴趣可以了解一下.本次升级主要增加以下功能: 日志搜索保存: 通过日志搜索保存可以把常用的搜索保存起来,下次可以更方便的进行查询. web日志报表: 专门对web日志增加了一个报表功能,可以提供pv,独立ip趋势图,http状态码分布,流量统计,ip访问排行和页面访问排行常用web统计报表. 增加了数据库采集: 首先在日志配置中进行增加. 在增加的页面中填写sql和主键信息,主键要是数字类型

Mysql更换MyISAM存储引擎为Innodb的操作记录

一般情况下,mysql会默认提供多种存储引擎,可以通过下面的查看: 1)查看mysql是否安装了innodb插件.通过下面的命令结果可知,已经安装了innodb插件. mysql> show plugins; +------------+--------+----------------+---------+---------+ | Name | Status | Type | Library | License | +------------+--------+----------------

php+mysql的微信文章发布平台

如何在微信上发表丰富图文的文章? 最近在新浪云平台上做了一个php+mysql的微信文章发布平台,丫丫说. 在线编辑文章,扫一扫即可分享到微信,发到朋友圈,非常简单! http://yayashuo.sinaapp.com   欢迎各位试用~

CentOS源码编译安装MySQL 5.5.15

CentOS源码编译安装MySQL 5.5.15 文章目录 [隐藏] 安装编译工具 下载源码 安装cmake和bison 编译安装MySQL 一些相关设置 安装编译工具 yum install gcc gcc-c++ yum install ncurses-devel 下载源码 mkdir -p /tmp cd /tmp wget http://dev.mysql.com/get/Downloads/MySQL-5.5/mysql-5.5.15.tar.gz/from/http://mysql.

解决MySQL 5.6版的Function 'innodb' already exists错误

解决MySQL 5.6版的Function 'innodb' already exists错误 作者:chszs,转载需注明.博客主页:http://blog.csdn.net/chszs MySQL 5.6启动后,其日志文件存在如下错误: ...... 2015-10-28 13:27:05 25054 [ERROR] Function 'innodb' already exists 2015-10-28 13:27:05 25054 [Warning] Couldn't load plugi

Delphi 7连接MySql 5.5.15

Delphi 7连接MySql 5.5.15 分类: 5.2 Delphi编程2011-09-26 17:12 12156人阅读 评论(0) 收藏 举报 delphimysql数据库microsoftdatabasewindows 网上有很多关于Delphi连接MySql数据库的文章,在这里,我只记录下自己测试过的方法,以备所需.系统环境:Windows XP SP3软件环境:Delphi 7 .mysql-installer-5.5.15.0 1.ODBC方式    必须要先有MySql的OD

MySQL数据库MyISAM存储引擎转为Innodb

MySQL数据库MyISAM存储引擎转为Innodb 之前公司的数据库存储引擎全部为MyISAM,数据量和访问量都不是很大,所以一直都没什么问题.但是最近出现了MySQL数据表经常被锁的情况,直接导致了用户连接网站时超时而返回502,于是决定把存储引擎转为Innodb的,以解决MyISAM的表锁问题.下面将操作步骤记录一下. 1.导出centos数据库的表结构 mysqldump -d -uxxx -p centos > centos_table.sql 其中-d参数表示不导出数据,只导出表结构