![]() ![]() Typically, when the mysqldump file is loaded, MySQL and InnoDB ignore CREATE TABLE options they do not recognize, and the table(s) are created in a format used by the running server. Therefore, be sure the new database is running the InnoDB storage engine, with the proper settings for innodb_file_format and innodb_file_per_table, if you want to have the tables re-created as they exist in the original database. WARNING: If you dump a database containing compressed tables with mysqldump, the dump file may contain CREATE TABLE statements that attempt to create compressed tables, or those using ROW_FORMAT=DYNAMIC in the new database. This ensures that the log files and other system information do not cause consistency issues or startup problems when using a prior version of MySQL. It is strongly recommended that you use a " slow shutdown" (SET GLOBAL innodb_fast_shutdown=0) when stopping the MySQL server before downgrading to MySQL 5.1 or earlier. WARNING: Once you create any tables with the Barracuda file format, take care to avoid crashes and corruptions when using those files with an earlier version of MySQL. Using MySQL Enterprise Backup or InnoDB Hot Backup. See Section 14.4.4.2.1, "Compatibility Check When InnoDB Is Started" for the details.ĭowngrading from MySQL 5.5 to the MySQL 5.1 or earlier (without the InnoDB Plugin enabled), or otherwise using earlier versions of MySQL with database files created by MySQL 5.5 and higher. To provide early feedback, InnoDB 1.1 checks the system tablespace before startup to ensure that the file format used in the database is supported by the storage engine. With previous versions of InnoDB, no error would be returned until you try to access a table that is in a format " too new" for the software. ![]() These references are cleared in a slow shutdown. However, the system tablespace may contain references to new-format tables that confuse the built-in InnoDB in MySQL 5.1 and earlier. InnoDB since version 5.0.21 has a safety feature that prevents it from opening tables that are in an unknown format. The new parameter innodb_file_format can help protect upward and downward compatibility between InnoDB versions and database files, allowing users to enable or disable use of new features that can only be used with certain versions of InnoDB. ![]() Existing databases can be used with the InnoDB Storage Engine for MySQL. The InnoDB storage engine is upward compatible from standard InnoDB as built in to, and distributed with, MySQL. The previous file format, used by the built-in InnoDB in MySQL 5.1 and earlier, is now called Antelope and does not support these features, but does support the other features introduced with the InnoDB storage engine. Note that the ability to use data compression and the new row format require the use of a new InnoDB file format called Barracuda. Section 14.4.8.8, "More Read-Ahead Statistics" Section 14.4.8.7, "More Compact Output of SHOW ENGINE INNODB MUTEX" Section 14.4.8.6, "Better Error Handling when Dropping Indexes" Section 14.4.8.5, "Controlling Optimizer Statistics Estimation" Section 14.4.8.3, "TRUNCATE TABLE Reclaims Space" Section 14.4.8.2, "Dynamic Control of System Configuration Parameters" Section 14.4.8.1, "The Barracuda File Format" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |