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 will 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.
As InnoDB evolves, new on-disk data structures are sometimes
required to support new features. Features such as compressed tables
(see Section 14.7, “InnoDB Compressed Tables”), long variable-length
columns stored off-page (see Section 14.9, “InnoDB Row Storage and Row Formats”),
and index key prefixes up to 3072 bytes
innodb_large_prefix) require data
file formats that are not compatible with prior versions of InnoDB.
These features require use of the
Barracuda file format.
This section discusses enabling file formats for new InnoDB tables, verifying compatibility of different file formats between MySQL releases, identifying the file format in use, and downgrading the file format.
Named File Formats.
InnoDB uses named file formats to help manage compatibility in
upgrade and downgrade situations, or heterogeneous systems running
different levels of MySQL. Currently,
Barracuda file formats are
supported. Barracuda is the
newest file format. It supports important InnoDB features such as
compressed tables and the
DYNAMIC row format
for more efficient BLOB storage. The original InnoDB file format,
which previously did not have a name, is now known as
InnoDB file format settings do not apply to tables stored in general tablespaces. General tablespaces provide support for all row formats and associated features. For more information, see Section 14.5.9, “InnoDB General Tablespaces”.