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-metrics-table.html
row *************************** NAME: dml_inserts SUBSYSTEM: dml COUNT: 3 MAX_COUNT: 3 MIN_COUNT: NULL AVG_COUNT: 0.046153846153846156 COUNT_RESET: 3 MAX_COUNT_RESET: 3 MIN_COUNT_RESET: NULL AVG_COUNT_RESET: NULL TIME_ENABLED: 2014-12-04 14:18:28 ...
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-innodb-trx-table.html
TRX_ROWS_MODIFIED The number of modified and inserted rows in this transaction. The INNODB_TRX table provides information about every transaction currently executing inside InnoDB, including whether the transaction is waiting for a lock, when the ...
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-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-deadlock-example.html
The following example illustrates how an error can occur when a lock request causes a deadlock. First, client A creates a table containing one row, and then begins a transaction. The lock cannot be granted because it is incompatible with the S lock ...
https://dev.mysql.com/doc/refman/5.7/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 ...