翻譯水平有限，供英語不太好的朋友做個參考，歡迎大家提意見。 官網(wǎng)鏈接 https://dev.MySQL.com/doc/refman/5.5/en/glossary.html 這些術(shù)語普遍應(yīng)用在mysql服務(wù)器的相關(guān)信息中。這個作為InnoDB存儲引擎相關(guān)術(shù)語的一個參考，而且多數(shù)的定義都和InnoDB相關(guān)。

.ARM file

ARCHIVE表的元數(shù)據(jù)。和.ARZ文件形成對比。以此作為擴展名的文件總是包含由MySQL EnterPRise Backup 的mysqlbackup命令生成的備份。 參見 .ARZ file, MySQL Enterprise Backup, mysqlbackup command。

.ARZ file

ARCHIVE表的數(shù)據(jù)。和.ARM文件形成對比。以此作為擴展名的文件總是包含由MySQL Enterprise Backup 的mysqlbackup命令生成的備份。 參見 .ARZ file, MySQL Enterprise Backup, mysqlbackup command。

ACID

這個大家都知道，就不羅嗦了。 參見atomic, commit, concurrency, doublewrite buffer, isolation level, locking, rollback, transaction。

adaptive flushing

這是一種為了緩解InnoDB表由檢查點引入的I/O開銷的算法。mysql定期地刷新修改頁的小集合，而不是把緩存池中的所有修改頁立即刷新到數(shù)據(jù)文件中。適應(yīng)性刷新算法通過評估執(zhí)行這些定期刷新的最佳比率，基于刷新比率和redo信息生成的速度，擴展了這個進程。 參見 buffer pool, checkpoint, data files, flush, InnoDB, page, redo log。

adaptive hash index

An optimization for InnoDB tables that can speed up lookups using = and IN 這是一種通過在內(nèi)存中構(gòu)建哈希索引，使用=和IN分隔符來加速InnoDB表的優(yōu)化手段。

Operators, by constructing a hash index in memory. MySQL monitors index searches for InnoDB tables, and if queries could benefit from a hash index, it builds one automatically for index pages that are frequently accessed. In a sense, the adaptive hash index configures MySQL at runtime to take advantage of ample main memory, coming closer to the architecture of main-memory databases. This feature is controlled by the innodb_adaptive_hash_index configuration option. Because this feature benefits some workloads and not others, and the memory used for the hash index is reserved in the buffer pool, typically you should benchmark with this feature both enabled and disabled. The hash index is always built based on an existing InnoDB secondary index, which is organized as a B-tree structure. MySQL can build a hash index on a prefix of any length of the key defined for the B-tree, depending on the pattern of searches against the index. A hash index can be partial; the whole B-tree index does not need to be cached in the buffer pool. In MySQL 5.6 and higher, another way to take advantage of fast single-value lookups with InnoDB tables is to use the InnoDB memcached plugin. See InnoDB memcached Plugin for details.

參見 B-tree, buffer pool, hash index, memcached, page, secondary index。