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/innodb-data-dictionary.html
The InnoDB data dictionary is comprised of internal system tables that contain metadata used to keep track of objects such as tables, indexes, and table columns. For historical reasons, data dictionary metadata overlaps to some degree with ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INNODB_TRX, INNODB_LOCKS, and INNODB_LOCK_WAITS) represents a glimpse into fast-changing data. For performance reasons, and to minimize the chance of misleading joins between the transaction ...This is not like user tables, where the data changes only when application-initiated updates ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-transactions.html
INNODB_LOCKS: Each transaction in InnoDB that is waiting for another transaction to release a lock (INNODB_TRX.TRX_STATE is LOCK WAIT) is blocked by exactly one blocking lock request. For every blocked transaction, INNODB_LOCKS contains one row that ...That blocking lock request is for a row or table lock held by another transaction in an incompatible ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb-innodb-workloads.html
A number of major differences in behavior between the NDB and InnoDB storage engines with regard to some common types of database-driven application workloads are shown in the following table:: Table 21.2 Differences between InnoDB and NDB storage ... NDB Cluster has a range of unique attributes that make it ideal to serve applications requiring high availability, fast failover, high throughput, and low ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb.html
InnoDB is the storage engine that MySQL customers typically use in production databases where reliability and concurrency are important. This section explains how to optimize database operations for InnoDB tables.
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-tuning-monitoring.html
This section builds on the performance tuning advice from Section 14.9.1.3, “Tuning Compression for InnoDB Tables”, and shows how to find problems that might not turn up during initial testing. The INNODB_CMP table reports information about ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlock-example.html
As a result, InnoDB generates an error for one of the clients and releases its locks. 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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-disk-management.html
Within these constraints, InnoDB tries to optimize the database work and the organization of disk files to minimize the amount of disk I/O. This section discusses the main considerations for I/O and disk space with the default kind of MySQL tables ... As a DBA, you must manage disk I/O to keep the I/O subsystem from becoming saturated, and manage disk space to avoid filling up storage ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-ddl.html
You can access the underlying InnoDB table (which is test.demo_test by default) through standard SQL interfaces. The InnoDB table is either IS (intention shared) or IX (intention exclusive) locked for all operations in a transaction. However, there ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-developing.html
Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or adapting existing code that uses MySQL or the memcached API. Both queries (read) and DML (write) operations can be substantially faster when ...