PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-table-reference.html
The following table summarizes INFORMATION_SCHEMA InnoDB tables. For greater detail, see the individual table descriptions. Table 24.3 INFORMATION_SCHEMA InnoDB Tables Table Name Description Deprecated INNODB_BUFFER_PAGE Pages in InnoDB buffer pool ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-introduction.html
Although you can select INFORMATION_SCHEMA as the default database with a USE statement, you can only read the contents of tables, not perform INSERT, UPDATE, or DELETE operations on them. INFORMATION_SCHEMA provides access to database metadata, ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-plugins-table.html
PLUGIN_STATUS The plugin status, one of ACTIVE, INACTIVE, DISABLED, or DELETED. The PLUGINS table has these columns: PLUGIN_NAME The name used to refer to the plugin in statements such as INSTALL PLUGIN and UNINSTALL PLUGIN. PLUGIN_TYPE The type of ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-referential-constraints-table.html
The REFERENTIAL_CONSTRAINTS table has these columns: CONSTRAINT_CATALOG The name of the catalog to which the constraint belongs. CONSTRAINT_SCHEMA The name of the schema (database) to which the constraint belongs. UNIQUE_CONSTRAINT_CATALOG The name ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-table-reference.html
The following table summarizes all available INFORMATION_SCHEMA tables. For greater detail, see the individual table descriptions. Table 24.1 INFORMATION_SCHEMA Tables Table Name Description Introduced Deprecated CHARACTER_SETS Available character ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/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/5.7/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/5.7/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/5.7/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 ...