Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-tp-thread-state-table.html
Note The INFORMATION_SCHEMA thread pool tables are deprecated, and subject to removal in a future version of MySQL. You should use the versions available as Performance Schema tables instead. Applications should transition away from the old tables ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-backup-recovery.html
This section covers topics related to InnoDB backup and recovery. For information about backup techniques applicable to InnoDB, see Section 17.18.1, “InnoDB Backup”. For information about point-in-time recovery, recovery from disk failure or ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-optimization.html
InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory. Knowing how the InnoDB buffer pool works, and taking advantage of it to keep frequently accessed data in memory, is an important aspect of MySQL tuning.
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-resize.html
You can configure InnoDB buffer pool size offline or while the server is running. For additional information about configuring buffer pool size online, see Configuring InnoDB Buffer Pool Size Online. When increasing or decreasing ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed data. However, because the efficiency of compression depends on the nature of your data, you can make decisions ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-disk-io.html
InnoDB uses asynchronous disk I/O where possible, by creating a number of threads to handle I/O operations, while permitting other database operations to proceed while the I/O is still in progress. On Linux and Windows platforms, InnoDB uses 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.html
This section provides information and usage examples for InnoDB INFORMATION_SCHEMA tables. InnoDB INFORMATION_SCHEMA tables provide metadata, status information, and statistics about various aspects of the InnoDB storage engine. You can view a list ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-limits.html
This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. The index key prefix length limit is 3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format. The index key prefix ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-migration.html
This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL instance to a larger, faster server; you might clone an entire MySQL instance to a new ...