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. * 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 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |