https://dev.mysql.com/innodb-ft-index-table-table.html
The same word can occur several times within the cache table, once for each combination of DOC_ID and POSITION values. The INNODB_FT_INDEX_TABLE table provides information about the inverted index used to process text searches against the FULLTEXT ...
https://dev.mysql.com/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 ...INNODB_CMPMEM and INNODB_CMPMEM_RESET provide information about the way memory is allocated for ...
https://dev.mysql.com/innodb-information-schema-examples.html
SELECT THREAD_ID, SQL_TEXT FROM performance_schema.events_statements_history WHERE THREAD_ID = 28 ORDER BY EVENT_ID; Sometimes it is useful to correlate internal InnoDB locking information with the session-level information maintained by MySQL.
https://dev.mysql.com/innodb-information-schema-internal-data.html
Data retrieved from the lock tables exists when the SELECT is executed, but might be gone or changed by the time the query result is consumed by the client. Note This section describes locking information as exposed by the Performance Schema ...
https://dev.mysql.com/innodb-information-schema-understanding-innodb-locking.html
At any given time, a transaction may request a lock that is held by another transaction, in which case it is blocked by that other transaction. Note This section describes locking information as exposed by the Performance Schema data_locks and ...
https://dev.mysql.com/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE= clause creates an InnoDB table. Key ...
https://dev.mysql.com/innodb-linux-native-aio.html
With synchronous I/O, query threads queue I/O requests, and InnoDB background threads retrieve the queued requests one at a time, issuing a synchronous I/O call for each. InnoDB uses the asynchronous I/O subsystem (native AIO) on Linux to perform ...
https://dev.mysql.com/innodb-locking-reads.html
Here, FOR SHARE is not a good solution because if two users read the counter at the same time, at least one of them ends up in deadlock when it attempts to update the counter. If you query data and then insert or update related data within the same ...
https://dev.mysql.com/innodb-memcached-porting-memcached.html
Changes to the innodb_memcache.containers table take effect the next time the innodb_memcache.containers table is queried. This is because InnoDB performs best for large-scale insertions if primary key values are added in sorted order (as they are ...
https://dev.mysql.com/innodb-memcached-porting-mysql.html
The results are already converted; # no need to repeat conversion functions and WHERE clauses each time. mysql> INSERT INTO innodb_memcache.containers (name,db_schema,db_table,key_columns,value_columns,flags,cas_column, ... Consider these aspects of ...
