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 Cloud Sites MySQL servers 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博客 ” ，链接：https://blog.itpub.net/26477398/viewspace-2122430/ ，如需转载，请注明出处，否则将追究法律责任。
