Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-usage.html
Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system tablespace (space 0, the .ibdata files) can contain user-created tables, but it also contains internal system data, which is never compressed.
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks-handling.html
This section builds on the conceptual information about deadlocks in Section 17.7.5.2, “Deadlock Detection”. It explains how to organize database operations to minimize deadlocks and the subsequent error handling required in applications.
https://dev.mysql.com/doc/refman/8.4/en/innodb-disk-management.html
As a DBA, you must manage disk I/O to keep the I/O subsystem from becoming saturated, and manage disk space to avoid filling up storage devices. The ACID design model requires a certain amount of I/O that might seem redundant, but helps to ensure ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-compression-tables.html
There are two pairs of InnoDB INFORMATION_SCHEMA tables about compression that can provide insight into how well compression is working overall: INNODB_CMP and INNODB_CMP_RESET provide information about the number of compression operations and the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-fulltext_index-tables.html
INNODB_FT_BEING_DELETED: Provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the INNODB_FT_BEING_DELETED table is emptied, and DOC_ID values are removed from ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INFORMATION_SCHEMA INNODB_TRX table, Performance Schema data_locks and data_lock_waits tables) represents a glimpse into fast-changing data. This is not like user tables, where the data ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-tables.html
For related information and examples, see Section 17.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 ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-understanding-innodb-locking.html
When a transaction updates a row in a table, or locks it with SELECT FOR UPDATE, InnoDB establishes a list or queue of locks on that row. Similarly, InnoDB maintains a list of locks on a table for table-level locks. If a second transaction wants to ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be configured before initializing InnoDB. Modifying the configuration after InnoDB is initialized ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-multi-versioning.html
It keeps information about old versions of changed rows to support transactional features such as concurrency and rollback. This information is stored in undo tablespaces in a data structure called a rollback segment. InnoDB uses the information in ...