MariaDB 10 – XtraDB & InnoDB versions
MariaDB
I’ve had this question several times when presenting and once via an internal email thread so I figure I might as well write about it:What is the default transactional engine in MariaDB 10.0? The answer is simple – it is XtraDB.
However this answer has some history: initial releases of MariaDB 10 actually shipped with InnoDB from MySQL 5.6. Only in 10.0.9 RC did the default switch back to being XtraDB. As MariaDB users previously know, XtraDB was the default InnoDB in 5.1, 5.2, 5.3, and 5.5 too. As always, you can switch easily between InnoDB/XtraDB – read more in:Using InnoDB instead of XtraDB.
How do you tell what version of InnoDB or XtraDB you are running? Simply, run: SHOW GLOBAL VARIABLES LIKE 'innodb_version';
MariaDB 10.0 (read more:What is MariaDB 10.0):
Version | InnoDB | XtraDB | Status | Date |
10.0.10 | 5.6.15 | 5.6.15-63.0* | GA | 31 Mar 2014 |
10.0.9 | 5.6.15 | 5.6.15-63.0* | RC | 10 Mar 2014 |
10.0.8 | 5.6.14* | 5.6.14-62.0 | RC | 10 Feb 2014 |
10.0.7 | 5.6.10* | 5.6.14-62.0 | Beta | 27 Dec 2013 |
10.0.6 | 1.2.6 * | n/a | Beta | 18 Nov 2013 |
10.0.5 | 1.2.5 * | n/a | Beta | 7 Nov 2013 |
10.0.4 | 1.2.4 * (5.6.10merge) | n/a | Alpha | 16 Aug 2013 |
10.0.3 | 10.0.3-MariaDB * | n/a | Alpha | 11 Jun 2013 |
10.0.2 | 10.0.2-MariaDB * | n/a | Alpha | 24 Apr 2013 |
10.0.1 | 1.2.1 * | n/a | Alpha | 6 Feb 2013 |
10.0.0 | 1.2.0 (5.6.5merge) | n/a | Alpha | 12 Nov 2012 |
The asterisk (*) denotes the default engine choice.
Why are there odd InnoDB versions from 10.0.0 – 10.0.6? I can only point this to merge oddities.storage/innobase/include/univ.iis the file which contains common definitions such as INNODB_VERSION_MAJOR,INNODB_VERSION_MINORandINNODB_VERSION_BUGFIX.INNODB_VERSION_BUGFIXin 10.0.6 pointed toMYSQL_VERSION_PATCHwhich you get from theVERSIONfile. For XtraDB, you will also seePERCONA_INNODB_VERSIONinuniv.i.
So, when XtraDB is the default (10.0.9 and 10.0.10 and releases going forward) you can put in my.cnf to load InnoDB:
ignore_builtin_innodbplugin_load=innodb=ha_innodb.so
When InnoDB is the default (10.0.8 and 10.0.7) and XtraDB was merged, you can put in my.cnf to load XtraDB:
ignore_builtin_innodbplugin_load=innodb=ha_xtradb.so
Percona Server only became GA with5.6.13-61.0which was 7 Oct 2013 which explains why the MariaDB 10.0.6 beta didn’t include a XtraDB.
Percona Server only ships XtraDB (source code instorage/innobase) while MariaDB ships both InnoDB (storage/innobase) as well as XtraDB (storage/xtradb).
If you want older release information about InnoDB plugin versions, a great resource is Chris Calendar’s blog post:InnoDB Plugin Versions. I’m just glad that going forward the InnoDB version will just match the release version as you can see with 10.0.7 and later.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

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.

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL is suitable for small and large enterprises. 1) Small businesses can use MySQL for basic data management, such as storing customer information. 2) Large enterprises can use MySQL to process massive data and complex business logic to optimize query performance and transaction processing.

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.
