Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-table-reference.html
The following table summarizes all available INFORMATION_SCHEMA tables. For greater detail, see the individual table descriptions. Table 28.1 INFORMATION_SCHEMA Tables Table Name Description Deprecated ADMINISTRABLE_ROLE_AUTHORIZATIONS Grantable ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-benefits.html
Inserts, updates, and deletes are optimized by an automatic mechanism called change buffering. InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what was happening in ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning-monitoring.html
A large number of compression operations overall (compared to the number of INSERT, UPDATE and DELETE operations in your application and the size of the database) could indicate that some of your compressed tables are being updated too heavily for ... Overall application performance, CPU and I/O utilization and the size of disk files are good indicators of how effective compression is for your ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlock-detection.html
InnoDB tries to pick small transactions to roll back, where the size of a transaction is determined by the number of rows inserted, updated, or deleted. When deadlock detection is enabled (the default), InnoDB automatically detects transaction ...
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 ...