MySQL 8.0 Release Notes
MySQL 8.0 Source Code Documentation
- 26.4.1 INFORMATION_SCHEMA InnoDB Table Reference
- 26.4.2 The INFORMATION_SCHEMA INNODB_BUFFER_PAGE Table
- 26.4.3 The INFORMATION_SCHEMA INNODB_BUFFER_PAGE_LRU Table
- 26.4.4 The INFORMATION_SCHEMA INNODB_BUFFER_POOL_STATS Table
- 26.4.5 The INFORMATION_SCHEMA INNODB_CACHED_INDEXES Table
- 26.4.6 The INFORMATION_SCHEMA INNODB_CMP and INNODB_CMP_RESET Tables
- 26.4.7 The INFORMATION_SCHEMA INNODB_CMPMEM and INNODB_CMPMEM_RESET Tables
- 26.4.8 The INFORMATION_SCHEMA INNODB_CMP_PER_INDEX and INNODB_CMP_PER_INDEX_RESET Tables
- 26.4.9 The INFORMATION_SCHEMA INNODB_COLUMNS Table
- 26.4.10 The INFORMATION_SCHEMA INNODB_DATAFILES Table
- 26.4.11 The INFORMATION_SCHEMA INNODB_FIELDS Table
- 26.4.12 The INFORMATION_SCHEMA INNODB_FOREIGN Table
- 26.4.13 The INFORMATION_SCHEMA INNODB_FOREIGN_COLS Table
- 26.4.14 The INFORMATION_SCHEMA INNODB_FT_BEING_DELETED Table
- 26.4.15 The INFORMATION_SCHEMA INNODB_FT_CONFIG Table
- 26.4.16 The INFORMATION_SCHEMA INNODB_FT_DEFAULT_STOPWORD Table
- 26.4.17 The INFORMATION_SCHEMA INNODB_FT_DELETED Table
- 26.4.18 The INFORMATION_SCHEMA INNODB_FT_INDEX_CACHE Table
- 26.4.19 The INFORMATION_SCHEMA INNODB_FT_INDEX_TABLE Table
- 26.4.20 The INFORMATION_SCHEMA INNODB_INDEXES Table
- 26.4.21 The INFORMATION_SCHEMA INNODB_METRICS Table
- 26.4.22 The INFORMATION_SCHEMA INNODB_SESSION_TEMP_TABLESPACES Table
- 26.4.23 The INFORMATION_SCHEMA INNODB_TABLES Table
- 26.4.24 The INFORMATION_SCHEMA INNODB_TABLESPACES Table
- 26.4.25 The INFORMATION_SCHEMA INNODB_TABLESPACES_BRIEF Table
- 26.4.26 The INFORMATION_SCHEMA INNODB_TABLESTATS View
- 26.4.27 The INFORMATION_SCHEMA INNODB_TEMP_TABLE_INFO Table
- 26.4.28 The INFORMATION_SCHEMA INNODB_TRX Table
- 26.4.29 The INFORMATION_SCHEMA INNODB_VIRTUAL Table
This section provides table definitions for
INFORMATION_SCHEMA InnoDB
tables. For related information and examples, see
Section 15.15, “InnoDB INFORMATION_SCHEMA Tables”.
INFORMATION_SCHEMA InnoDB
tables can be used to monitor ongoing InnoDB
activity, to detect inefficiencies before they turn into issues, or
to troubleshoot performance and capacity issues. As your database
becomes bigger and busier, running up against the limits of your
hardware capacity, you monitor and tune these aspects to keep the
database running smoothly.