In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. ![]() InnoDB: but the index tree has been freed! InnoDB: Error: trying to load index index_name for table table_name ![]() * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: This issue is only likely to occur on 32-bit platforms. If this issue occurs, restart the server to work around it. * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. The fix speeds up the processing for freeing entries in the adaptive hash index. * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE statement for InnoDB tables, especially on systems with a large buffer pool. * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the optimizer for queries against partitioned InnoDB tables were based only on the first partition of each such table, leading to use of the wrong execution plan. Nothing is different for users of Oracle RPM packages. This change affects only users of Red Hat (or Red Hat-compatible) RPM packages. MySQL-shared-compat now replaces the Red Hat mysql-libs package by replacing libmysqlclient.so files of the latter package, thus satisfying dependencies of other packages on mysql-libs. ![]() * The MySQL-shared-compat RPM package enables users of Red Hat-privided mysql-*-5.1 RPM packages to migrate to Oracle-provided MySQL-*-5.5 packages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |