軟體下載 MySQL 5.6.23 (32-bit)

檔案名稱 mysql-5.6.23-win32.msi

MySQL 5.6.23 (32-bit) 軟體下載

軟體資訊
檔案版本 MySQL 5.6.23 (32-bit)

檔案名稱 mysql-5.6.23-win32.msi
檔案大小 44.73 MB
更新日期 2015-02-03
  • 1
    版本確認
  • 2
    檔案準備中
  • 3
    檔案下載

軟體介紹 & 更新資訊

MySQL 5.6.23 (32-bit)
MySQL 專為企業組織提供關鍵業務數據庫應用程序而設計。它為企業開發人員,數據庫管理員和 ISV 提供了一系列新的企業功能,以提高開發,部署和管理工業強度應用程序的效率.如果您需要 MySQL 數據庫的 GUI,可以下載 - NAVICAT(MySQL GUI)。它支持將 MySQL,MS SQL,MS Access,Excel,CSV,XML 或其他格式導入到 MySQL.MySQL 數據庫... MySQL (32-bit) 軟體介紹

What's new in this version:

Security Notes:
- The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1j to version 1.0.1k.
- This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug #20375530) Functionality Added or Changed:
- Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. Support was added for the TLS 1.1 and TLS 1.2 protocols. (Bug #19820550)
- References: See also Bug #19921150
- yaSSL was upgraded to version 2.3.7. (Bug #19695101, Bug #20201864)
- The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. (Bug #18366947) Bugs Fixed:
- InnoDB: A tablespace export operation set the purge state to PURGE_STATE_STOP but the purge thread did not check the purge state until the current purge operation was completed. In the case of a large history list, the tablespace export operation was delayed, waiting for the current purge operation to finish. The purge state is now checked with every purge batch. (Bug #20266847, Bug #75298)
- InnoDB: An ALTER TABLE ... ADD INDEX operation raised an assertion due to assertion code that did not allow an online index status of ONLINE_INDEX_ABORTED_DROPPED. The assertion code has been relaxed. (Bug #20198726)
- InnoDB: An error occurred when the push_warning_printf function was invoked during server recovery. This function was previously used to print a warning message to the client. Also, current_thd was NULL when the server was restarted. (Bug #20144839)
- InnoDB: An ALTER TABLE operation that changed the name of a foreign key column resulted in a failure when reloading the foreign key constraint. The previous column name remained in the data dictionary cache instead of being evicted. (Bug #20031243)
- InnoDB: Error messages regarding a size limitation on BLOB or TEXT data inserted in a single transaction have been revised. (Bug #19975322)
- InnoDB: DML operations on a table with full-text search indexes raised an invalid assertion. (Bug #19905246)
- References: This bug is a regression of Bug #19314480.
- InnoDB: A multiple-table delete operation caused the server to halt. (Bug #19815702)
- InnoDB: A FLUSH TABLES operation raised an assertion. (Bug #19803418)
- InnoDB: With change buffering enabled, a buffered sequence of operations that should not have been buffered resulted in an Unable to purge a record error. (Bug #19528825, Bug #73767)
- InnoDB: On non-Windows platforms, os-file_pread and os_file_pwrite functions return -1 when an error occurs. This value was printed in an error message as the number of bytes read or written. Instead of printing the -1 value in the error message, a separate error message indicating a system call failure is now printed. Thanks to David Bennett for the patch. (Bug #19315210, Bug #73365)
- InnoDB: A slow shutdown (innodb_fast_shutdown=0) after crash recovery raised an assertion. Slow shutdown did not wait for background rollback operations to finish before proceeding. (Bug #16862810)
- InnoDB: The integer column value was handled incorrectly for the memcached incr and decr commands. (Bug #69415, Bug #20083106, Bug #74874, Bug #20044123)
- Partitioning: A failed ALTER TABLE ... TRUNCATE PARTITION statement or a failed TRUNCATE TABLE statement against a partitioned table sometimes left inconsistent metadata in the table cache; subsequent SQL statements reusing this metadata failed, and could in some cases also lead to a failure of the server. (Bug #74292, Bug #19786861)
- Replication: If a client thread on a slave executed FLUSH TABLES WITH READ LOCK while the master executed a DML, executing SHOW SLAVE STATUS in the same client became blocked, causing a deadlock. The fix ensures that the read lock is only held during the period that the relay log is being updated and the deadlock is avoided. (Bug #19843808)
- Replication: When an XA transaction was active, executing an internal rollback, for example using the BINLOG statement, resulted in an assertion. The fix ensures that a rollback happens only for a slave when a transaction spans multiple binary log files. Rollback does not happen now if the Format_description comes from the BINLOG statement being executed in the MySQL client. (Bug #74597, Bug #19928622)
- Replication: In normal usage, it is not possible for a slave to have more GTIDs than the master. But in certain situations, such as after a hardware failure or incorrectly cleared gtid_purged, the master's binary log could be truncated. This fix ensures that in such a situation, the master now detects that the slave has transactions with GTIDs which are not on the master. An error is now generated on the slave and the I/O thread is stopped with an error. The master's dump thread is also stopped. This prevents data inconsistencies during replication. (Bug #72635, Bug #18789758)
- Replication: When using SHOW SLAVE STATUS to monitor replication performance, Seconds_Behind_Master sometimes displayed unexpected lag behind the master. This was caused by Previous_gtids_log_events being written to the slave's relay log with a timestamp behind the master, and then being used to calculate the Seconds_Behind_Master. This fix ensures that events generated on the slave that are added to the relay log and are not used when calculating Seconds_Behind_Master. (Bug #72376, Bug #18622657)
- On Ubuntu 14.10, MySQL install operations could fail to reload AppArmor. (Bug #20092641)
- EXPLAIN within an XA transaction could raise an assertion. (Bug #19941492)
- Binary log files created by streaming the binary log from a remote server with mysqlbinlog were given an access mode more permissive than the original files. (Bug #19649868)
- If the audit_log plugin encountered a disk-full error, the server would exit.
- Now, if the file system to which the audit log is being written fills up, a “disk full” error is written to the error log. Audit logging continues until the audit log buffer is full. If free disk space has not been made available by the time the buffer fills, client sessions will hang, and stopping the server at the time of client sessions hanging will result in audit log corruption. To avoid this if client sessions are hung, ensure that free space is available on the audit logging file system before stopping the server. (Bug #19411485)
- For failure to create a temporary table due to being out of file descriptors, the server exited rather than returning an error. (Bug #18948649)
- For some queries that contained a derived table (subquery in the FROM clause), delay of materialization resulted in a suboptimal execution plan due to a less accurate row-count estimate. (Bug #18607971)
- For UPDATE and DELETE statements, the server could exit after attempting to access an uninitialized data structure. (Bug #18036143)
- Starting the server with start service or mysqld_safe could result in failure to use the correct plugin directory. (Bug #17619241)
- FLUSH TABLES on a FEDERATED table failed if the table had been idle longer than the wait_timeout time plus the TCP keepalive time. (Bug #17599258)
- Selecting all columns from INFORMATION_SCHEMA.TABLES did not reopen tables if they were in the table cache, but selecting a subset of those columns under the same conditions did reopen tables. (Bug #16869534)
- If my_write() encountered a disk-full condition, it could return an incorrect error value. (Bug #16078792, Bug #19984788)
- InnoDB boolean full-text searches incorrectly handled + combined with parentheses; for example, +word1 +(>word2

MySQL 5.6.23 (32-bit) 相關參考資料
32位win7+vs2008編譯mysql 5.6.22源碼並安裝

2015年2月3日 — 標籤:以下這部分安裝說明是來自http://www.2cto.com/database/201407/316681.html的win7+vs2010源碼編譯mysql,文章最後會說明用vs2008編譯遇見的 ...

https://topic.alibabacloud.com

Download MySQL 5.6.23 for Windows

2023年6月5日 — Download MySQL 5.6.23 for Windows. Fast downloads of the latest free software! Click now.

https://filehippo.com

Download MySQL Community Server (Archived Versions)

8.0.32, 8.0.31, 8.0.30, 8.0.28, 8.0.27, 8.0 ... 5.6.23, 5.6.22, 5.6.21, 5.6.20, 5.6.19, 5.6.17, 5.6.16 ... Linux - Generic (glibc 2.28) (x86, 64-bit), Compressed ...

https://downloads.mysql.com

Download MySQL Installer (Archived Versions)

To download the latest release of MySQL Installer, please visit MySQL Downloads. Product Version: 8.0.36, 8.0.35, 8.0.34, 8.0.33, 8.0.32 ... 5.6.23, 5.6.22, 5.6.

https://downloads.mysql.com

Downloading MySQL 5.6.23 (32-bit) from FileHorse.com

MySQL is an open-source, community-driven RDBMS that provides a robust and scalable platform for storing, managing, and retrieving data.

https://www.filehorse.com

mysql 5.6.23 源码包安装报错_Mysql-5.6-快速安装

2021年2月1日 — mysql 5.6.23 源码包安装报错_Mysql-5.6-快速安装 原创 · 一,编译安装所需的工具和库. yum install gcc gcc-c++ ncurses-devel perl cmake -y · 二,新增 ...

https://blog.csdn.net

MySQL :: Download MySQL Community Server (Archived ...

Linux - Generic (glibc 2.5) (x86, 32-bit), RPM Bundle · 295.8M · (MySQL-5.6.23-1.linux_glibc2.5.i386.rpm-bundle.tar) ; Linux - Generic (glibc 2.5) (x86, 64-bit), ...

https://downloads.mysql.com

MySQL Download Free - 5.6.23

2015年2月2日 — MySQL. 5.6.23. Popular open source database. What's New. Specs. Download options: Windows 32-bit · Windows 64-bit · macOS. Serving tech ...

https://www.techspot.com

MySQL Installer - (Archived Versions)

To download the latest release of MySQL Installer, please visit MySQL Downloads. Product Version: 8.0.36, 8.0.35, 8.0.34, 8.0.33, 8.0.32 ... 5.6.23, 5.6.22, 5.6.

https://downloads.mysql.com

Windows 系统中安装MySQL 5.6 zip 步骤并配置root 密码原创

2015年8月9日 — MySQL 5.6 版本和5.7 版本的安装步骤有很大不同,本文记录了5.6 版本的安装步骤。 另外,如果开发者本机是Windows8、Windows10,要使用“命令提示符(管理员) ...

https://blog.csdn.net