设为首页收藏本站我的广告

运维网

 找回密码
 注册

QQ登录

只需一步,快速开始

扫一扫,访问微社区

搜索
总共321条微博

每日一博

查看: 679|回复: 0

[更新动态] 【重大新闻】 MySQL 5.6.27/5.5.46 发布【顶】

[复制链接]

该用户从未签到

totoonet 发表于 2015-10-2 00:11:54 | 显示全部楼层 |阅读模式
【重大新闻】

MySQL 5.6.27/5.5.46 发布

MySQL 5.6.27/5.5.46 发布
MySQL 5.6.27 发布,暂未放出发行说明,现已提供下载:
http://dev.mysql.com/downloads/mysql/

同时发布了 MySQL 5.5.46 版本,此版本更新 yaSSL 到 2.3.8/2.3.7d,其他主要是 bug 修复:


  • InnoDB: A data corruption occurred on ARM64. GCC builtins did not issuethe correct fences when setting or unsetting the lock word.   (Bug #21102971, Bug #76135)
  • InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch. (Bug #21025880, Bug #76927)
  • InnoDB:  The IBUF_BITMAP_FREE bit indicated that therewas more free space in the leaf page than was actually available.  (Bug #20796566)
  • InnoDB: Setting lower_case_table_names=0 on acase-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with thewrong tbl_name letter case. An error  message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.  (Bug #20198490, Bug #75185)
  • Partitioning:  CREATE TABLE statements that used an invalid function in a subpartitioning expression did notalways fail gracefully as expected.  (Bug #20310212)
  • Partitioning: ALTER TABLE when executed from astored procedure did not always work correctly with tablespartitioned by RANGE. (Bug #16613004)
  • Certain subqueries as arguments to PROCEDUREANALYSE() could cause a server exit.  (Bug #21350175)
  • mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.)  (Bug #21335818)
  • An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback. (Bug #21096444)
  • Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several  seconds after startup.  (Bug #21025377)
  • For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition.       (Bug #20909518)
  • DELETE could check privileges for the wrong database when table aliases were used.  (Bug #20777016)
  • Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit.       (Bug #20760261)
  • MySQL sometimes produced no warning when it was unable to interpret a character in a given character set.       (Bug #20238729)
  • For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit.  (Bug #20168526)
  • Execution of certain BINLOG  statements while temporary tables were open by HANDLER statements could cause a server exit. (Bug #19894987, Bug #20449914)
  • On Windows, setting query_cache_min_res_unit to too large a value could result in a value of 0 and a subsequent server exit. (Bug #18487951)
  • RPM installation scripts if configuration files contained multiple datadir lines. Now the last datadir line is used. (Bug #77878, Bug #21527467)
  • For wait events, the Performance Schema uses the CYCLE timer by default, but failed to fall back to a different timer if CYCLE was  unavailable.  (Bug #77577, Bug #21374104)
  • Updating VARCHAR and TEXT columns in the same UPDATE statement could produce incorrect results. When a VARCHARcolumn was assigned to a TEXT column and the VARCHAR column was then set to a different value, the TEXT column's result containedthe VARCHAR column's new value.  (Bug #77135, Bug #21143080)
  • mysqladmin -u root -p could exit with a segmentation fault. (Bug #76538, Bug #20802751)
  • mysqlimport --use-threads did not actually use multiple threads. (Bug #76480, Bug #20772273)
  • View creation from a UNION failed with a duplicate-column error if a SELECT statement in the        UNION other than the first used the same column name multiple times.(Bug #74539, Bug #19886430)
  • Empty XML elements having the form <element/> were not handled correctly by the LOAD XML statement. (Bug #67542, Bug #16171518)
更多内容请看更新日志

源自:网络
运维网 感谢您的阅读
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|申请友链|sitemap|手机版|小黑屋|Archiver|运维网 ( 京ICP备16008201号  

GMT+8, 2016-12-7 16:35 , Processed in 0.102181 second(s), 40 queries , Xcache On.

Powered by Discuz! X3.2 Licensed

© 2001-2013 Comsenz Inc.

快速回复 返回顶部 返回列表