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-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
INFORMATION_SCHEMA InnoDB tables can be used to monitor ongoing InnoDB activity, to detect inefficiencies before they turn into issues, or to troubleshoot performance and capacity issues. For related information and examples, see Section 14.16, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-understanding-innodb-locking.html
For a lock to be acquired by a transaction, all incompatible lock requests previously entered into the lock queue for that row or table must be removed (which occurs when the transactions holding or requesting those locks either commit or roll back). 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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-init-startup-configuration.html
On systems with a large amount of memory, you can improve concurrency by dividing the buffer pool into multiple buffer pool instances. The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page ...
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
The data stored through the daemon_memcached plugin goes into VARCHAR, TEXT, or BLOB columns, and must be converted to do numeric operations. Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-intro.html
You can map multiple columns into the “value” part of the key-value store, with column values delimited by a user-specified separator character. The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-replication.html
set test1 10 0 1 t1 STORED On the source server, check that the record was inserted into the demo_test table. Because the daemon_memcached plugin supports the MySQL binary log, updates made on a source server through the memcached interface can be ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-tuning.html
Because using InnoDB in combination with memcached involves writing all data to disk, whether immediately or sometime later, raw performance is expected to be somewhat slower than using memcached by itself. When using the InnoDB memcached plugin, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached.html
The InnoDB memcached plugin (daemon_memcached) provides an integrated memcached daemon that automatically stores and retrieves data from InnoDB tables, turning the MySQL server into a fast “key-value store”. Instead of formulating queries in ...