ADD PRIMARY KEY The fix preserves the original table if the server halts during this operation. An example of such an operation is ALTER TABLE. * InnoDB: If the server crashed at a precise moment during an ALTER TABLE operation that rebuilt the clustered index for an InnoDB table, the original table could be inaccessible afterward. * InnoDB: The server could halt with an assertion error while creating an index: InnoDB: Assertion failure in thread thread_num in file line 465 This issue affected tables with a combination of ROW_FORMAT=REDUNDANT off-page columns, and an index on a column prefix. * InnoDB: Creating an index on a CHAR column could fail for a table with a character set with varying length, such as UTF-8, if the table was created with the ROW_FORMAT=REDUNDANT clause. * InnoDB: The status variable Innodb_buffer_pool_read_ahead_evicted could show an inaccurate value, higher than expected, because some pages in the buffer pool were incorrectly considered as being brought in by read-ahead requests. This issue was observed on Solaris 64-bit systems. * InnoDB: On systems that cannot handle unaligned memory access, depending on the stack frame alignment, a SIGBUS error could occur during startup. In addition, the entire table is analyzed after first being rebuilt. All partitions will be rebuilt and analyzed. Now in such cases, the warning message is, Table does not support optimize on partitions. * InnoDB Partitioning: Previously, when attempting to optimize one or more partitions of a partitioned table that used a storage engine that does not support partition-level OPTIMIZE, such as InnoDB, MySQL reported Table does not support optimize, doing recreate + analyze instead, then re-created the entire table, but did not actually analyze it. The fix improves the accuracy of the index statistics gathered when the table is first created, and prevents the query plan from being changed by the ALTER TABLE statement. The issue went away following an ALTER TABLE on the table. * InnoDB Performance: Immediately after a table was created, queries against it would not use loose index scans. The check for whether any related changes needed to be merged from the insert buffer was being called more often than necessary. * InnoDB Performance: Optimized read operations for compressed tables by skipping redundant tests. * InnoDB Performance: Some data structures related to undo logging could be initialized unnecessarily during a query, although they were only needed under specific conditions.
Mysql download for windows 10 64 bit full version free keygen#
* In RPM packages built for Unbreakable Linux Network, libmysqld.so now has a version number.
This option records each deadlock condition in the MySQL error log, allowing easier troubleshooting if frequent deadlocks point to application coding issues. * InnoDB: The innodb_print_all_deadlocks configuration option from MySQL 5.6 was backported to MySQL 5.5.
0 kommentar(er)
