MySQL 存储引擎-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

MySQL 存储引擎

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 01, 2016 pm 01:14 PM

Skilltechnologyability

简介

MySQL中的数据用各种不同的技术存储在文件（或者内存）中；
每一种技术都使用不同的存储机制、索引技巧、锁定水平并且最终提供广泛的功能和能力；
这些不同的实现数据存储的技术在MySQL的整体架构中逻辑化为“存储引擎层”；
存储引擎，通常又被称作“表类型”（即可以在创建表时指定存储引擎，但无法对某一数据库指定存储引擎）

查看

show engines; # 显示可支持的存储引擎show table status [{from|in} Db_Name] [like ‘pattern’|where expr]; # 可显示指定数据库中指定表的状态信息# 法一：show table status like ‘classes’;# 法二：show table status where Name=’classes’/G

可通过查看表的状态信息获得表所使用的存储引擎类别：

修改默认存储引擎：

# 在配置文件/etc/my.cnf中设置如下：default_storage_engine = InnoDB

各存储引擎及其特性

InnoDB

支持事务：事务日志；日志文件大小一致：如ib_logfile0和ib_logfile1支持外键支持MVCC支持聚簇索引支持行级锁：即间隙锁支持辅助索引支持自适应hash索引支持热备份不支持全文索引

MyISAM

支持全文索引支持压缩：用于实现数据仓库，能节约存储空间并提升性能支持空间索引支持表级锁：若读写操作比例为9:1或8:2，则使用MyISAM可以提高性能延迟更新索引：减少IO压力不支持事务，外键，MVCC，行级锁等崩溃后无法安全恢复数据适用场景：多读少写的数据，较小的表，能够容忍崩溃后的修改操作和数据丢失；如自带的mysql数据库中的表都是使用MyISAM存储引擎的# 建议：使用InnoDB存储引擎，并使用read commited的隔离级别，性能并不比MyISAM性能差，故推荐使用InnoDB存储引擎

ARCHIVE

仅支持insert和select支持很好的压缩功能不支持事务，不能很好的支持索引适用于：存储日志信息，或其它按时间序列实现的数据采集类的应用，如监控日志

CSV

12	`将数据存储为csv格式，不支持索引仅适用于数据交换场景`

BLACKHOLE

12	`没有存储机制，任何发往此引擎的数据都会丢弃由于其会记录二进制日志，故常用于多级复制架构中作中转服务器`

MEMORY

1234	`数据保存在内存中，即是一个内存表` `仅支持hash索引，使用表级锁` `不支持blob和text数据类型常用于保存中间数据，如周期性的聚合数据等；也用于实现临时表`

MRG_MYISAM

12	`是MyISAM的一个变种，能够将多个MyISAM表合并为一个虚表属于传统的存储引擎，一般不常用`

NDB

1	`是MySQL Cluster中专用的存储引擎，不常用`

第三方的存储引擎

XtraDB

增强的InnoDB，由Percona提供；用法：编译安装MySQL时，下载XtraDB的源码替换MySQL存储引擎中的InnoDB源码，并重新编译安装MySQL

PBXT

MariaDB自带此存储引擎支持引擎级别的复制，外键约束支持事务，MVCC对SSD磁盘提供适当支持

TokuDB

使用Fractal Trees索引，性能很强适用于存储大数据，拥有很好的压缩比已被引入新版本的MariaDB

列式存储引擎：

Infobright

前身为Maria，是增强版的MyISAM支持崩溃后安全恢复支持数据缓存

其它列式存储引擎

如 InfiniDB，MonetDB，LucidDB等

开源社区存储引擎:

Aria

前身为Maria，是增强版的MyISAM支持崩溃后安全恢复支持数据缓存

Groona

全文索引引擎；Mroonga是基于Groona的二次开发版

OQGraph

由Open Query研发，支持图结构的存储引擎

SphinxSE

为Sphinx全文搜索服务器提供了SQL接口

Spider

能将数据切分成不同的分片，比较高效透明的实现了分片(shard)；支持在分片上支持并行查询

选择存储引擎可参考要素

是否需要事务

备份的类型的支持(热备或冷备)

崩溃后的恢复

特有的特性(如对SSD的支持等)

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Explain the role of InnoDB redo logs and undo logs.Apr 15, 2025 am 12:16 AM

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

What are the key metrics to look for in an EXPLAIN output (type, key, rows, Extra)?Apr 15, 2025 am 12:15 AM

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

What is the Using temporary status in EXPLAIN and how to avoid it?Apr 15, 2025 am 12:14 AM

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

Describe the different SQL transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) and their implications in MySQL/InnoDB.Apr 15, 2025 am 12:11 AM

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL vs. Other Databases: Comparing the OptionsApr 15, 2025 am 12:08 AM

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

See all articles