Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual Excerpts from this Manual

MySQL 5.7 Reference Manual  /  The InnoDB Storage Engine  /  InnoDB File-Format Management

14.7 InnoDB File-Format Management

As InnoDB evolves, data file formats that are not compatible with prior versions of InnoDB are sometimes required to support new features. To help manage compatibility in upgrade and downgrade situations, and systems that run different versions of MySQL, InnoDB uses named file formats. InnoDB currently supports two named file formats, Antelope and Barracuda.

This section discusses enabling file formats for new InnoDB tables, verifying compatibility of different file formats between MySQL releases, and identifying the file format in use.

InnoDB file format settings do not apply to tables stored in general tablespaces (introduced in MySQL 5.7.6). General tablespaces provide support for all row formats and associated features. For more information, see Section 14.4.9, “InnoDB General Tablespaces”.


The following file format configuration parameters have new default values as of MySQL 5.7.7:

  • The innodb_file_format default value was changed to Barracuda. The previous default value was Antelope.

  • The innodb_large_prefix default value was changed to ON. The previous default was OFF.

The following file format configuration parameters are deprecated in MySQL 5.7.7 and may be removed in a future release:

The file format configuration parameters were provided for creating tables compatible with earlier versions of InnoDB in MySQL 5.1. Now that MySQL 5.1 has reached the end of its product lifecycle, the parameters are no longer required. Future removal of the innodb_file_format parameter will require a new mechanism for managing compatibility of InnoDB tables and tablespaces among different versions of MySQL.

Download this Manual
User Comments
Sign Up Login You must be logged in to post a comment.