MySQL Storage Engines
16.1 Setting the Storage Engine 16.2 The MyISAM Storage Engine 16.3 The MEMORY Storage Engine 16.4 The CSV Storage Engine 16.5 The ARCHIVE Storage Engine 16.6 The BLACKHOLE Storage Engine 16.7 The MERGE Storage Engine 16.8 The FEDERATED Storage Engine 16.9 The EXAMPLE Storage Engine 16.10 Other Storage Engines 16.11 Overview of MySQL Storage Engine Architecture
The two most commonly used table engines on are Innodb and MyISAM.
Table 16.1 Storage Engines Feature Summary
Feature | MyISAM | Memory | InnoDB | Archive | NDB |
---|---|---|---|---|---|
Storage limits | 256TB | RAM | 64TB | None | 384EB |
Transactions | No | No | Yes | No | Yes |
Locking granularity | Table | Table | Row | Row | Row |
MVCC | No | No | Yes | No | No |
Geospatial data type support | Yes | No | Yes | Yes | Yes |
Geospatial indexing support | Yes | No | Yes[a] | No | No |
B-tree indexes | Yes | Yes | Yes | No | No |
T-tree indexes | No | No | No | No | Yes |
Hash indexes | No | Yes | No[b] | No | Yes |
Full-text search indexes | Yes | No | Yes[c] | No | No |
Clustered indexes | No | No | Yes | No | No |
Data caches | No | N/A | Yes | No | Yes |
Index caches | Yes | N/A | Yes | No | Yes |
Compressed data | Yes[d] | No | Yes[e] | Yes | No |
Encrypted data[f] | Yes | Yes | Yes | Yes | Yes |
Cluster database support | No | No | No | No | Yes |
Replication support[g] | Yes | Yes | Yes | Yes | Yes |
Foreign key support | No | No | Yes | No | No |
Backup / point-in-time recovery[h] | Yes | Yes | Yes | Yes | Yes |
Query cache support | Yes | Yes | Yes | Yes | Yes |
Update statistics for data dictionary | Yes | Yes | Yes | Yes | Yes |
[a] InnoDB support for geospatial indexing is available in MySQL 5.7.5 and higher. [b] InnoDB utilizes hash indexes internally for its Adaptive Hash Index feature. [c] InnoDB support for FULLTEXT indexes is available in MySQL 5.6.4 and higher. [d] Compressed MyISAM tables are supported only when using the compressed row format. Tables using the compressed row format with MyISAM are read only. [e] Compressed InnoDB tables require the InnoDB Barracuda file format. [f] Implemented in the server (via encryption functions). Data-at-rest tablespace encryption is available in MySQL 5.7 and higher. [g] Implemented in the server, rather than in the storage engine. [h] Implemented in the server, rather than in the storage engine. |
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26477398/viewspace-2122430/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MYSQL TABLE CHANGE STORAGE ENGINEMySql
- php新浪雲連結mysql與storagePHPMySql
- HTML5 game enginesHTMLGAM
- The Storage Situation: Removable StorageREM
- DB-Engines:2019年全球最受歡迎資料庫 MySQL奪冠資料庫MySql
- storage事件中的坑,storage.setItem()無法觸發storage事件事件
- Database StorageDatabase
- MySQL:ERROR 1286 (42000): Unknown storage engine 'MyISAM'MySqlError
- ECMAScript 5 compatibility shims for legacy JavaScript enginesJavaScript
- JavaScript storage 事件JavaScript事件
- Web Storage概述Web
- Kafka Offset StorageKafka
- Physical Storage StructuresStruct
- Password Storage - UserDetailsAI
- MySQL ERROR 1031 (HY000) at line 33: Table storage engine forMySqlError
- DB-Engines 11 月最新資料庫排名資料庫
- Display Storage Map for Database | Tablespace | Datafile Storage_1377458.1Database
- DB-Engines 2019 年度資料庫出爐:MySQL 成為年度資料庫贏家資料庫MySql
- cookie、session、web storageCookieSessionWeb
- Docker storage儲存Docker
- Btree Index storage internalIndex
- Storage location 地址資訊
- SAP WM Storage Type Search配置裡的Storage Class & WPC標記
- DB-Engines:2013年4月份全球資料庫排名 Oracle排名第一 MySQL第二資料庫OracleMySql
- ASM(Automatic Storage Management)ASM
- 【ionic】storage本地快取快取
- Azure 基礎:File Storage
- Azure 基礎:Table storage
- Azure 基礎:Blob Storage
- Azure 基礎:Queue Storage
- 【PingCAP】Database Storage EngineerPingCAPDatabase
- SAP WM高階之Storage Type上架策略L下的Mixed Storage
- SAP MM 物料主資料Plant Data Storage 1檢視裡的Storage Bin
- 微信小程式storage儲存微信小程式
- Automatic Storage Management (ASM)(轉)ASM
- k8s-storage-classK8S
- Nebula Storage 2.0 儲存格式
- 【HTML5】Web Storage 事件HTMLWeb事件