PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.3Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
MySQL and Linux/Unix
MySQL and macOS
MySQL Partitioning
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL Restrictions and Limitations
Security in MySQL
MySQL and Solaris
Building MySQL from Source
Starting and Stopping MySQL
MySQL Tutorial
MySQL and Windows
MySQL NDB Cluster 7.5
AsInnoDB evolves, data file formats that are not compatible with prior versions ofInnoDB 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 andBarracuda.
Antelope is the original
InnoDBfile format, which previously did not have a name. It supports theCOMPACT andREDUNDANT row formats forInnoDBtables.Barracuda is the newest file format. It supports all
InnoDBrow formats including the newerCOMPRESSED andDYNAMIC row formats. The features associated withCOMPRESSED andDYNAMIC row formats include compressed tables, efficient storage of off-page columns, and index key prefixes up to 3072 bytes (innodb_large_prefix). SeeSection 14.11, “InnoDB Row Formats”.
This section discusses enablingInnoDB file formats for newInnoDB 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 ingeneral tablespaces. General tablespaces provide support for all row formats and associated features. For more information, seeSection 14.6.3.3, “General Tablespaces”.
The following file format configuration parameters have new default values:
The
innodb_file_formatdefault value was changed toBarracuda. The previous default value wasAntelope.The
innodb_large_prefixdefault value was changed toON. The previous default wasOFF.
The following file format configuration parameters are deprecated in and may be removed in a future release:
The file format configuration parameters were provided for creating tables compatible with earlier versions ofInnoDB in MySQL 5.1. Now that MySQL 5.1 has reached the end of its product lifecycle, the parameters are no longer required.
PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.3Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
MySQL and Linux/Unix
MySQL and macOS
MySQL Partitioning
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL Restrictions and Limitations
Security in MySQL
MySQL and Solaris
Building MySQL from Source
Starting and Stopping MySQL
MySQL Tutorial
MySQL and Windows
MySQL NDB Cluster 7.5