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-disk-management.html
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 devices. The ACID design model requires a certain amount of I/O that might seem redundant, but helps to ensure ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-compression-tables.html
There are two pairs of InnoDB INFORMATION_SCHEMA tables about compression that can provide insight into how well compression is working overall: INNODB_CMP and INNODB_CMP_RESET provide information about the number of compression operations and the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-fulltext_index-tables.html
INNODB_FT_BEING_DELETED: Provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the INNODB_FT_BEING_DELETED table is emptied, and DOC_ID values are removed from ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-tables.html
For related information and examples, see Section 14.16, “InnoDB INFORMATION_SCHEMA Tables”. INFORMATION_SCHEMA InnoDB tables can be used to monitor ongoing InnoDB activity, to detect inefficiencies before they turn into issues, or to ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-understanding-innodb-locking.html
When a transaction updates a row in a table, or locks it with SELECT FOR UPDATE, InnoDB establishes a list or queue of locks on that row. Similarly, InnoDB maintains a list of locks on a table for table-level locks. If a second transaction wants to ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-init-startup-configuration.html
The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be configured before initializing InnoDB. Modifying the configuration after InnoDB is initialized ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locking-reads.html
If you query data and then insert or update related data within the same transaction, the regular SELECT statement does not give enough protection. Other transactions can update or delete the same rows you just queried. InnoDB supports two types of ...
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. With the daemon_memcached plugin, instead of many traditional memcached servers ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-intro.html
The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB storage engine directly, bypassing the MySQL SQL layer. The following diagram illustrates how an application accesses data through the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-replication.html
Because the daemon_memcached plugin supports the MySQL binary log, updates made on a source server through the memcached interface can be replicated for backup, balancing intensive read workloads, and high availability. You do not need to set up ...