MariaDB 5.1 is no longer maintained. Please use a more recent release.
30 Jan 2013
MariaDB 5.1.67
Stable (GA)
In short, is a binary drop in replacement of MySQL 5.1, but with performance like MySQL 5.5 (thanks to XtraDB), fewer bugs, and more features. Thanks to the extended and improved program it's also easier to upgrade from MySQL 5.0 to MariaDB 5.1 than to MySQL 5.1.
MariaDB 5.1 is based on MySQL 5.1. We do a merge once a month with MySQL5.1 to ensure all MySQL bug fixes get into MariaDB.
See also:
: A crash-safe storage engine based on MyISAM.
: Drop-in replacement for InnoDB based on the InnoDB plugin.
): A transactional storage engine with a lot of nice features.
: Drop-in replacement for Federated.
is faster.
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 result sets with all characters between 0x00-0x7f.
Our use of the Aria 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. Aria is usually faster for temporary tables when compared to MyISAM because Aria caches row data in memory and normally doesn't have to write the temporary rows to disk.
(New optimization) (MWL#17)
(Allows you to have 200,000+ connections to MariadB)
MariaDB can handle up to 32 key segments per key (up from 16)
Added --abort-source-on-error to the mysql client.
We have made it to
InnoDB and Archive tables are now upgraded properly.
More options to and to find out what's going on.
Cleaned up wrong warnings from mysqlcheck.
(Upgrading from MySQL 5.1 to MariaDB 5.1 is a trivial 1 min exercise as MariaDB is a binary drop in replacement of MySQL. Just remove MySQL and install MariaDB and things will just work )
More tests in the test suite.
All tests runs now clean without having to restart test. (Oracle re-runs tests 3 times and assumes things are ok if one tests works)
Test builds with different configure options to get better feature testing.
Remove invalid tests. (e.g. Don't test feature "X" if that feature is not in the build you are testing.)
A build is not regarded ok if there are any errors or compiler warnings.
We have fixed a lot of bugs in the MySQL code which we have found while merging the MySQL code into MariaDB and by running the extended test suite.
For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the page.
: : : : : : : : : , : : : : : : : : : : : : : : : : : : :
The following CVEs are also fixed in but the fix is not tied to a specific version number:
29 Nov 2012
MariaDB 5.1.66
Stable (GA)
6 Apr 2012
MariaDB 5.1.62
Stable (GA)
2 Apr 2012
MariaDB 5.1.61
Stable (GA)
5 Dec 2011
MariaDB 5.1.60
Stable (GA)
1 Mar 2011
MariaDB 5.1.55
Stable (GA)
6 Dec 2010
MariaDB 5.1.53
Stable (GA)
19 Nov 2010
MariaDB 5.1.51
Stable (GA)
9 Sep 2010
MariaDB 5.1.50
Stable (GA)
9 Aug 2010
MariaDB 5.1.49
Stable (GA)
1 Jun 2010
MariaDB 5.1.47
Stable (GA)
10 May 2010
MariaDB 5.1.44b
Stable (GA)
24 Mar 2010
MariaDB 5.1.44
Stable (GA)
1 Feb 2010
MariaDB 5.1.42
Stable (GA)
13 Jan 2010
MariaDB 5.1.41
Release Candidate
15 Nov 2009
MariaDB 5.1.39
Beta
29 Oct 2009
MariaDB 5.1.38
Beta
This page is licensed: CC BY-SA / Gnu FDL