Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks.html
A deadlock is a situation in which multiple transactions are unable to proceed because each transaction holds a lock that is needed by another one. Because all transactions involved are waiting for the same resource to become available, none of ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
If you have transactions that update, insert, or delete many rows, you might consider increasing the size of the log buffer to save disk I/O. The first decisions to make about InnoDB configuration involve the configuration of data files, log files, ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-introduction.html
With foreign keys, inserts, updates, and deletes are checked to ensure they do not result in inconsistencies across related tables. InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-migration.html
There are no unmerged insert buffer entries in the .ibd file. 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, ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-limitations.html
Secondary indexes are not created as efficiently because keys are inserted in the order they appeared in the primary key. The following limitations apply to online DDL operations: The table is copied when creating an index on a TEMPORARY TABLE. The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute with CREATE TABLE or ALTER TABLE. Supported Platforms Page compression requires sparse ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-compression-oltp.html
The rise of SSD storage devices, which are fast but relatively small and expensive, makes compression attractive also for OLTP workloads: high-traffic, interactive websites can reduce their storage requirements and their I/O operations per second ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-schema.html
This section provides a brief introduction to InnoDB integration with Performance Schema. For comprehensive Performance Schema documentation, see Chapter 29, MySQL Performance Schema. You can profile certain internal InnoDB operations using the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-purge-configuration.html
When the purge lag exceeds the innodb_max_purge_lag threshold, a delay is imposed on INSERT, UPDATE, and DELETE operations to allow time for purge operations to catch up. InnoDB does not physically remove a row from the database immediately when ...