The most recent release in the MariaDB 5.1 series is:MariaDB 5.1.67
Download | Release Notes | Changelog |Overview of 5.1
Release date: 29 Oct 2009
See the MariaDB versus MySQL page for a high-level overview of the differences between MariaDB and MySQL.
MariaDB 5.1.38 Beta is based on MySQL 5.1.38 and XtraDB 1.0.3-6.
MariaDB will be kept up to date with the latest MySQL release from the same branch.
In most respects MariaDB will work exactly as MySQL; all commands, interfaces,libraries and APIs that exist in MySQL also exist in MariaDB.
For 5.1.38, the main differences between MariaDB and MySQL are:
The storage engine version 1.5 (the crash-safe version) is included in the source and binaries by default.
If you use the source, you can of course easily disable the Maria storage engine when configuring .
The new Maria storage engine specific options can be found here:.
replaces InnoDB in the tree.
XtraDB is a drop in replacement of InnoDB (same table formats, no need to convert any data).
XtraDB gives you similar performance improvements for multi-cpu systems in that you can expect from using InnoDB in MySQL 5.4.
See also
The storage engine version 1.0.08d is included in the source and binaries by default.
See also:
Our use of the Maria storage engine enables faster complex queries (queries which normally use disk-based temporary tables).
The storage engine is used for internal temporary tables, which should give you a speedup when doing complex selects. Maria is usually faster for temporary tables when compared to MyISAM because Maria caches row data in memory and normally doesn't have to write the temporary rows to disk.
Limited sets of threads handling all queries.
See:
Fewer warnings when compiling. We believe that compiler warnings can indicate bugs, and strive toward reduction to 0.
Fewer bugs. If we see a bug while fixing a warning or cleaning up code, we'll fix it when possible.
There are some improvements to DBUG code to make its execution faster when debug is compiled in but not used.
CHECKSUM TABLE now ignores values inNULL fields. This makes CHECKSUM TABLE
faster and fixes some cases where the same table definition could give
different checksum values depending on row format. The disadvantage is the
value is now different compared to other MySQL installations. The new
checksum calculation is fixed for all table engines which use the default way
to calculate and MyISAM which does the calculation internally. Note: Old
MyISAM tables with internal checksum will return the same checksum as before.
To fix them to calculate according to new rules you have to do anALTER TABLE. You can use the old ways to calculate
checksums by using the option --old to mysqld or set the
system variable '
MariaDB can handle up to 32 key segments per key (up from 16)
Added a new handler function: prepare_index_scan() that is called before a key scan is done.
Added --abort-source-on-error to the mysql client.
Wrong mutex usage detector. This helps us find and fix deadlocks when taking mutex in inconsistent orders. In MariaDB we have removed several deadlocks which exist in the normal MySQL code.
Implementation of : Table elimination
See for details.
This is based on the patch from .
See for details.
This is based on the patch from .
See for details.
@@oldCHECKSUM TABLE ... EXTENDED;We have eliminated/improved some not needed character set conversions. Overall speed improvements is 1-5 % (according to sql-bench) but can be higher for big results sets with all characters between 0x00-0x7f.
This page is licensed: CC BY-SA / Gnu FDL