Changes & Improvements in MariaDB 5.3
MariaDB 5.3 is no longer supported. Please use a more recent release.
|30 Jan 2013||MariaDB 5.3.12||Stable (GA)||Release Notes||Changelog|
|29 Nov 2012||MariaDB 5.3.11||Stable (GA)||Release Notes||Changelog|
|13 Nov 2012||MariaDB 5.3.10||Stable (GA)||Release Notes||Changelog|
|02 Oct 2012||MariaDB 5.3.9||Stable (GA)||Release Notes||Changelog|
|28 Aug 2012||MariaDB 5.3.8||Stable (GA)||Release Notes||Changelog|
|4 May 2012||MariaDB 5.3.7||Stable (GA)||Release Notes||Changelog|
|9 Apr 2012||MariaDB 5.3.6||Stable (GA)||Release Notes||Changelog|
|29 Feb 2012||MariaDB 5.3.5||Stable (GA)||Release Notes||Changelog|
|15 Feb 2012||MariaDB 5.3.4||Release Candidate||Release Notes||Changelog|
|21 Dec 2011||MariaDB 5.3.3||Release Candidate||Release Notes||Changelog|
|14 Oct 2011||MariaDB 5.3.2||Beta||Release Notes||Changelog|
|10 Sep 2011||MariaDB 5.3.1||Beta||Release Notes||Changelog|
|26 July 2011||MariaDB 5.3.0||Beta||Release Notes||Changelog|
- Feature Comparison Matrix
- Query optimizer
- NoSQL-style interfaces
- Replication and binary logging
- Windows performance improvements
- Security Vulnerabilities Fixed in MariaDB 5.3
The focus for MariaDB 5.3 is to radically improve performance for subqueries, as well as for joins and single-table queries over large data sets.
MariaDB 5.3 is based on MariaDB 5.2 and thus on MariaDB 5.1 and MySQL 5.1. It is no longer being supported.
Some of the code was backported from MySQL 6.0 (a MySQL version that was never released as GA by Oracle), some was re-engineered and enriched by new features, and some code was written from scratch.
Any new feature or combination of features can be switched on/off dynamically via the optimizer_switch system variable.
The first stable (GA) release of MariaDB 5.3 was MariaDB 5.3.5, which was released on 29 Feb 2012.
You can download the latest binaries of MariaDB 5.3 here, or get the latest source code from launchpad.
Feature Comparison Matrix
We have created an Optimizer Feature Comparison Matrix showing the new optimizer features in MariaDB 5.5 and 5.3 compared to MySQL 5.5 and 5.6.
Subqueries are finally usable in practice. It is no longer necessary to
rewrite subqueries manually into joins or into separate queries. MariaDB 5.3
aims to provide reasonably efficient handling for all kinds of subqueries.
All problems with
EXPLAIN taking a long time have also been resolved.
- Semi-join subquery optimizations
These transform subqueries into 'semi-joins', entities similar to inner joins, and then use join optimizer to pick the best semi-join execution strategy. Overall the process is similar to how joins are processed in MySQL,MariaDB and other database systems.
- Non-semi-join optimizations
If a subquery is not a semi-join, MariaDB 5.3 will make a cost-based choice between these two strategies:
- Materialization for non-correlated subqueries, with efficient NULL-aware execution
- IN-to-EXISTS transformation (the only optimization inherited from MariaDB 5.2 and MySQL 5.1/5.5)
- Subquery Cache
The subquery cache makes sure that subqueries are re-executed as few times as possible, improving performance of already optimized subqueries.
- Subqueries are never executed during
EXPLAIN, thus resulting in almost instant
- DISTINCT and GROUP BY without HAVING are optimized away from subqueries.
The Subquery Optimizations Map shows new subqueries optimizations graphically.
Optimizations for derived tables and views
- No early materialization of derived tables (e.g. subqueries in a
FROMclause) and materialized views (
EXPLAINis always instantaneous)
- Thanks to Derived Table Merge optimization, mergeable derived tables are now processed like mergeable VIEWs.
- Derived Table with Keys optimization gives the optimizer an option to create indexes over materialized derived tables
- Fields of merge-able views and derived tables are involved now in all optimizations employing equalities
Disk access optimization
- Index Condition Pushdown
- Multi-Range-Read optimization (MRR)
- Key-ordered retrieval
- Block-based Join Algorithms
- Block Nested Loop algorithm can be used for outer joins
- Block Hash Join (classic algorithm) is implemented and can be used for any equi-joins
- Block Index Join (Batch Key Access Join) is supported and can exploit the benefits of ordered retrievals for primary and secondary keys provided by the new implementation of MRR
- All block based algorithms for joins can use the benefits of new incremental join buffers
- All block based algorithms fully support outer joins including nested outer joins
- All block based algorithms can use the benefits of the first match optimization for semi-joins and the non-exist optimization for outer joins
- All block based algorithms for joins can exploit the benefits of index condition push-down.
- The total memory space used by the query for join buffers can be limited now, and block based algorithms can allocate join buffers up to their needs (not exceeding the set limits).
- Condition over outer tables extracted from ON expressions of outer joins are evaluated before inner tables are accessed (supported for both regular index join and block index join)
- Early checks for nulls for the fields from any null-rejecting conditions are performed
Index Merge improvements
- Correct optimization of index_merge vs range access: Fair choice between range and index_merge optimizations
- index_merge/sort_intersection strategy
- @@optimizer_switch variable can be used to turn on/off all new optimizations.
- HandlerSocket plugin included.
- Faster HANDLER commands; HANDLER READ now also work with prepared statements.
- Dynamic Columns support.
Replication and binary logging
- Group commit for the binary log — MariaDB 5.3 implements group commit which works when using XtraDB with the binary log enabled. (In previous MariaDB releases, and all MySQL releases at the time of writing, group commit works in InnoDB/XtraDB when the binary log is disabled, but stops working when the binary log is enabled).
- Annotation of row-based replication events with the original SQL statement — When using row-based replication, the binary log does not contain SQL statements, only discrete single-row insert/update/delete events. This can make it harder to read mysqlbinlog output and understand where in an application a given event may have originated, complicating analysis and debugging.This feature adds an option to include the original SQL statement as a comment in the binary log (and shown in mysqlbinlog output) for row-based replication events.
- Checksums for binlog events. This is a backport of the same feature in MySQL 5.6. It was implemented in MWL#180.
- Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT —
In MariaDB 5.3,
START TRANSACTION WITH CONSISTENT SNAPSHOTnow also works with the binary log. This means it is possible to obtain the binlog position corresponding to a transactional snapshot of the database without blocking any other queries. This is used by the command "
" to do a fully non-blocking backup which can be used to provision a new slave. "
SNAPSHOT" now also works consistently between transactions involving more than one storage engine (currently XTraDB and PBXT support this).
- Row-based replication for tables with no primary key —
This feature can improve the performance of row-based replication on tables
that do not have a primary key (or other unique key), but which do have
another index that can help locate rows to update or delete. With this
feature, index cardinality information from
ANALYZE TABLEis considered when selecting the index to use (before this feature is implemented, the first index was selected unconditionally).
mysqlbinlogwill now omit redundant
ROLLBACKevents when reading MySQL 5.0 binlogs.
- Microsecond support for NOW() and timestamp, time, and datetime columns.
- CAST() now supports AS DECIMAL[(M,D)] and AS INT.
- CAST() and all other datetime/time functions now supports microsecond fully.
Windows performance improvements
- Backported Windows performance patches from MySQL 5.5.
- Asynchronous IO in XtraDB is redesigned and is now faster, due to the use of IO completion ports.
- Additional durability option for XtraDB :
innodb_flush_methodcan now be
O_DSYNC, like on Unixes. The effect of using this option is that the log file is opened with
FlushFileBuffers()is not done. This may improve speed in write-heavy scenarios.
- A new Windows MSI installer.
- Includes a GUI-tool, HeidiSQL.
- GIS precise operations
- New status variables:
Handler_tmp_updatewhich count what happens with internal temporary tables.
Handler_updateno longer count operations on internal temporary tables.
- New status variable
Handler_read_rnd_deleted, which is number of deleted rows found and skipped while scanning a table. Before this was part of
- New variable 'in_transaction' that is 1 if you are in a transaction, 0 otherwise.
- Progress reports for
LOAD DATA INFILE. In addition Aria tables gives progress reports for
CHECK TABLE. The progress can be seen in
INFORMATION_SCHEMA.PROCESSLISTand is sent to MariaDB clients that calls
mysql_real_connect()with the new
mysqlcommand line client supports the new progress indications.
- PBXT consistent commit ordering —
This feature implements the new commit ordering storage engine API in PBXT.
With this feature, it is possible to use
START TRANSACTION WITH CONSISTENT SNAPSHOT" and get consistency among transactions which involve both XtraDB and InnoDB. (Without this feature, there is no such consistency guarantee. For example, even after running "
START TRANSACTION WITH CONSISTENT SNAPSHOT" it was still possible for the InnoDB/XtraDB part of some transaction T to be visible and the PBXT part of the same transaction T to not be visible.)
- MariaDB unique error numbers now start from
1900to not clash with MySQL error numbers.
/*M!##### */new executed comment syntax that can be used when you want use new MariaDB syntax but still want your program to be compatible with MySQL.
- A MariaDB optimized version of mytop is included in the MariaDB distribution.
- Enhanced KILL syntax:
KILL [HARD | SOFT] [CONNECTION | QUERY] [thread_id | USER user_name]
max_user_connections(both the global variable and the
GRANToption) can be set to
-1to stop users from connecting to the server. The global
max_user_connectionsvariable does not affect users with the
- The IGNORE directive does not ignore all errors (like fatal errors), only things that are safe to ignore.
You can access the MariaDB 5.3 tree from launchpad.
Security Vulnerabilities Fixed in MariaDB 5.3
For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the Security Vulnerabilities Fixed in MariaDB page.
- CVE-2013-1531: MariaDB 5.3.12
- CVE-2013-0389: MariaDB 5.3.12
- CVE-2013-0385: MariaDB 5.3.12
- CVE-2013-0384: MariaDB 5.3.12
- CVE-2013-0383: MariaDB 5.3.12
- CVE-2013-0375: MariaDB 5.3.12
- CVE-2012-5627: MariaDB 5.3.12 
- CVE-2012-5615: MariaDB 5.3.12 
- CVE-2012-5612: MariaDB 5.3.12
- CVE-2012-5611: MariaDB 5.3.12, MariaDB 5.3.11
- CVE-2012-4414: MariaDB 5.3.8 
- CVE-2012-1705: MariaDB 5.3.12
- CVE-2012-1702: MariaDB 5.3.12
- CVE-2012-0574: MariaDB 5.3.12
- CVE-2012-0572: MariaDB 5.3.12