What's new in this version: Functionality Added or Changed: - On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed: - InnoDB: A regression introduced by Bug #14329288 would result in a performance degradation when a compressed table does not fit into memory. - InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. - InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. - InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. - InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. - InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 - InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) - InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. - Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. - Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. - Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). - Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. - A shared libmysqld embedded server library was not built on Linux. - While printing the server version, the mysql client did not check for buffer overflow in a string variable. - Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. - DROP TRIGGER succeeded even with the read_only system variable enabled. - Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. - Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. - When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. - MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. - A deadlock error occurring during subquery execution could cause an assertion to be raised. - The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. - For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs.
MySQL 5.5.37 (64-bit) 相關參考資料
Download MySQL Community Server (Archived Versions)
5.5.37, 5.5.36, 5.5.35, 5.5.34, 5.5.33, 5.5.32, 5.5.31 ... Linux - Generic (glibc 2.28) (x86, 64-bit), Compressed TAR Archive ... Linux - Generic (glibc 2.28) (ARM, ...
https://downloads.mysql.com
Download MySQL Installer (Archived Versions)
5.5.37, 5.5.36, 5.5.35, 5.5.34, 5.5.33, 5.5.32, 5.5.31 ... Windows (x86, 32-bit). Windows (x86, 32-bit), MSI ... Windows (x86, 32-bit), MSI Installer, Jan 2, 2024 ...
https://downloads.mysql.com
Downloading MySQL 5.5.37 (64-bit) from FileHorse.com
The world`s most popular open-source relational database management system · MySQL 5.5.37 (64-bit) · Key details about this download.
https://www.filehorse.com
Index of MySQLDownloadsMySQL-5.5
Index of /MySQL/Downloads/MySQL-5.5/ ../ MySQL-5.5.60-1.el6.i686.rpm-bundle.tar 17-Apr-2018 10:33 144916480 MySQL ... 64bit.pkg.gz 26-Feb-2018 12:57 365679307 ...
http://ftp.ntu.edu.tw
install-source
... MySQL This chapter describes how to obtain and ... 5.5.37-linux-i686.tar.gz ... bit and 64-bit versions. For supported Windows platform information, see http ...
https://github.com
MariaDB 5.5.37 now available
2014年4月17日 — MariaDB 5.5.37 now available. Written ... file /usr/share/mysql/mysql.server from ... 36 packages which you are trying to upgrade with 64-bit 5.5.
https://mariadb.org
MariaDB 5.5.64 Release Notes
2019年4月29日 — In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
https://mariadb.com
MySQL 5.5.x < 5.5.37 MySQL 多個弱點
概要. 遠端資料庫伺服器可能受到多個弱點的影響。 說明. 遠端主機上安裝的MySQL 版本為比5.5.37 舊的5.5.x 版。因此可能受到'client/mysql.cc' 檔案和以下元件中的一個 ...
https://zh-tw.tenable.com
MySQL Community Server
Linux - Generic 2.6 (x86, 64-bit), RPM Package MySQL Server, Nov 5, 2014, 48.2M · Download ; (MySQL-server-5.5.41-1.linux2.6.x86_64.rpm), MD5: ...
https://downloads.mysql.com
mysql-devel-5.5.61-1.el6.remi RPM for x86_64
2018年8月17日 — real-mysql(x86-64) = 5.5.61-1.el6.remi; real ... 5.5.37-1 - update to MySQL 5.5.37 Community ... bit platforms that also define the 32-bit ...
https://rpmfind.net
|