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-adaptive-hash.html
The adaptive hash index enables InnoDB to perform more like an in-memory database on systems with appropriate combinations of workload and sufficient memory for the buffer pool without sacrificing transactional features or reliability. The adaptive ...Based on the observed pattern of searches, a hash index is built using a prefix of the index ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-consistent-read.html
A consistent read means that InnoDB uses multi-versioning to present to a query a snapshot of the database at a point in time. Consistent read is the default mode in which InnoDB processes SELECT statements in READ COMMITTED and REPEATABLE READ ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-create-table-external.html
There are different reasons for creating InnoDB tables externally; that is, creating tables outside of the data directory. InnoDB supports the following methods for creating tables externally: Using the DATA DIRECTORY Clause Using CREATE TABLE ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-defragmenting.html
All InnoDB data and indexes are stored in B-trees, and their fill factor may vary from 50% to 100%. To speed up index scans, you can periodically perform a “null” ALTER TABLE operation, which causes MySQL to rebuild the table: ALTER TABLE ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-next-key-locking.html
To prevent phantoms, InnoDB uses an algorithm called next-key locking that combines index-row locking with gap locking. InnoDB performs row-level locking in such a way that when it searches or scans a table index, it sets shared or exclusive locks ... The so-called phantom problem occurs within a transaction when the same query produces different sets of rows at different ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-midpoint_insertion.html
Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed again. For an explanation of the inner workings of the InnoDB buffer pool and specifics about ...The goal is to make sure that frequently accessed (“hot”) pages remain in the buffer pool, even as read-ahead and full table scans bring in new blocks that might or might not be accessed ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-statistics-estimation.html
Optimizer statistics are not persisted to disk when innodb_stats_persistent=OFF or when individual tables are created or altered with STATS_PERSISTENT=0. As of MySQL 5.6.6, optimizer statistics are persisted to disk by default, enabled by the ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-sys-columns-table.html
The INNODB_SYS_COLUMNS table provides metadata about InnoDB table columns, equivalent to the information from the SYS_COLUMNS table in the InnoDB data dictionary. For related usage information and examples, see Section 14.16.3, “InnoDB ...These ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-sys-datafiles-table.html
The INNODB_SYS_DATAFILES table provides data file path information for InnoDB file-per-table and general tablespaces, equivalent to the information in the SYS_DATAFILES table in the InnoDB data dictionary. For related usage information and ...If a ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks-handling.html
You can cope with deadlocks and reduce the likelihood of their occurrence with the following techniques: At any time, issue SHOW ENGINE INNODB STATUS to determine the cause of the most recent deadlock. If frequent deadlock warnings cause concern, ...