InnoDB evolves, data file formats that are not
compatible with prior versions of
sometimes required to support new features. To to help manage
compatibility in upgrade and downgrade situations, and systems that
run different versions of MySQL,
named file formats.
InnoDB currently supports two
named file formats, Antelope
Barracuda is the newest
file format. In addition to supporting
formats, Barracuda supports
InnoDB tables. The features
formats include compressed tables (see
Section 14.8, “InnoDB Row Storage and Row Formats”), off-page storage for long
column data (see Section 14.8, “InnoDB Row Storage and Row Formats”), and index
key prefixes up to 3072 bytes
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 following file format configuration parameters are deprecated in MySQL 5.7.7 and may be removed in a future release:
These configuration parameters were provided for creating tables
compatible with earlier versions of
MySQL 5.1. Now that MySQL 5.1 has reached the end of its product
lifecycle, the parameters are no longer required. Future removal
parameter would necessitate a new mechanism for managing
InnoDB tables and tablespaces
for different versions of MySQL.