Restrictions on InnoDB table objects

Restrictions on InnoDB table objects

Restrictions on InnoDB table objects:

Maximum and minimum

InnoDB log files cannot exceed 512 GB

InnoDB system tablespace requires at least 10 MB Space

The default data page size in the database is 16 kb.

The statistics collected by the analyze table statement are not particularly accurate,

The show table status statement cannot list the actual statistics of the InnoDB TABLE. information such as the number of record lines and average record length is only an estimate.

When the select count (*) from tbl statement is used, InnoDB must retrieve the entire table. MySQL recommends that you use this type of InnoDB Engine table to create an intermediate table to record the number of rows.

We recommend that you create a single column index for the AUTO_INCREMENT column.

Delete from tbl does not recreate a table, but deletes records one by one.

When the system variable innodb_table_locks is 1, lock tables holds two locks on the table. One is the LOCK held by the MySQL layer, and the other is the InnoDB layer also needs to hold a LOCK.

The locks held by the InnoDB engine in the transaction will be released when the transaction is committed or rolled back. Therefore, it is meaningless to execute the lock table when autocommit = 1, because the locks held will be released immediately.

MySQL innoDB Storage engine Learning

MySQL InnoDB Storage engine lock mechanism Experiment

Startup, shutdown, and restoration of the InnoDB Storage Engine

MySQL InnoDB independent tablespace Configuration

Architecture of MySQL Server layer and InnoDB Engine Layer

InnoDB deadlock Case Analysis

MySQL Innodb independent tablespace Configuration

This article permanently updates the link address: