Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
MariaDB 5.1 Series Release Notes
Download | Release Notes | Changelog |Overview of 5.1
Release date: 30 Jan 2013
This is a Stable (GA) release. In general this means that there are no known serious bugs, except for those marked as feature requests, that no bugs were fixed since last release that caused a notable code changes, and that we believe the code is ready for general usage (based on bug inflow).
For a description of MariaDB 5.1 see theWhat is MariaDB 5.1 page.
For a list of changes made in this release, with links to detailed information on each push, see the MariaDB 5.1.67 Changelog.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
This release is primarily a bug-fix release.
This release includes fixes for the following security vulnerabilities:
A buffer overflow that can cause a server crash or arbitrary code execution (a variant of )
DoS - server lockup ()
DoS - server crash ()
Additionally, it includes all security fixes from MySQL 5.1.67, such as fix for a buffer overflow with stored routines (a variant of ) and fixes for the following vulnerabilities:
This release includes MySQL 5.1.67. See for what changed in MySQL.
The MariaDB project tries to support as many different Operating Systems and Linux Distributions as we can. However, when a distribution or OS stops receiving security and other updates it becomes difficult to freely provide packages for that platform. In such cases, our policy is to deprecate that platform and stop providing binary packages for it.
As of 1 Feb 2013, we will stop building packages for the following:
Fedora 16 "Verne"
Debian 5 "Lenny"
Ubuntu 10.10 "Maverick"
Ubuntu 11.04 "Natty"
If your chosen Linux Distribution or Operating System is deprecated, packages or support are not completely unavailable. Companies such as and (and others) provide support for all versions of MariaDB back to even very old MySQL versions. This includes packaged binaries. Contact them for more details.
More information on our deprecation policy can be found at:
From the beginning of the MariaDB project in 2009 we've kept all of our old releases online via our network of mirrors. Doing this is great for those few who are interested in old releases, but the disk space required to host all of our old releases is over 130 Gigabytes at present and grows by several gigabytes with each new release. This is too much for some of our mirrors to handle. So, starting with this release our primary mirror will only host the most recent three or four releases in each series (5.5, 10.0, and so on). Mirrors are, of course, free to keep archiving every release, but the primary mirror that they pull from will not.
Old releases do have value, so for those that are interested in old releases, we are setting up a simple, no frills, archive server which will host them. Once the server is up and running, links to archived releases on will point at the archive server. During the transition period, links to some old releases may disappear for a short time, but don't worry, they haven't been deleted, they're just being moved!
Thanks, and enjoy MariaDB!
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: 6 Apr 2012
MariaDB 5.1.62 is a Stable (GA) release. In general this means that there are no known serious bugs, except for those marked as feature requests, that no bugs were fixed since last release that caused a notable code changes, and that we believe the code is ready for general usage (based on bug inflow).
For a description of MariaDB 5.1 see theWhat is MariaDB 5.1 page.
For a list of changes made in MariaDB 5.1.62, with links to detailed information on each push, see the MariaDB 5.1.62 Changelog.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
fixes a bug that under certain rare circumstances allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible.
This release includes fixes for the following security vulnerabilities:
This version of MariaDB includes MySQL 5.1.62. See for what changed between this and previous MySQL versions.
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: 2 Apr 2012
MariaDB 5.1.61 is a Stable (GA) release. In general this means that there are no known serious bugs, except for those marked as feature requests, that no bugs were fixed since last release that caused a notable code changes, and that we believe the code is ready for general usage (based on bug inflow).
For a description of MariaDB 5.1 see theWhat is MariaDB 5.1 page.
For a list of changes made in MariaDB 5.1.61, with links to detailed information on each push, see the MariaDB 5.1.61 Changelog.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
This version of MariaDB includes MySQL 5.1.61. See for what changed between this and previous MySQL versions.
Be notified of new releases automatically by adding the to your favorite feed reader or by to the announce 'at' mariadb.org announcement list (this is a low traffic, announce-only list).
MariaDB may already be included in your favorite OS distribution. More information can be found on the page.
The most recent release in the is:
|Release Notes | Release date: 29 Nov 2012
is a (GA) release. In general this means that there are no known serious bugs, except for those marked as feature requests, that no bugs were fixed since last release that caused a notable code changes, and that we believe the code is ready for general usage (based on bug inflow).
For a description of see the page.
For a list of changes made in , with links to detailed information on each push, see the .
In most respects will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
MariaDB 5.1.66 includes a fix for CVE-2012-5611, a vulnerability that allowed an authenticated user to crash MariaDB server or to execute arbitrary code with the privileges of the mysqld process. This is a serious security issue. We recommend upgrading from older versions as soon as possible.
A fix is also included for multiple SQL injection vulnerabilities in the replication code. See MDEV-382 (CVE-2012-4414) for details.
This release also includes fixes for the following security vulnerabilities:
This version of MariaDB includes MySQL 5.1.66. See Changes in MySQL 5.1.66 for what changed between this and previous MySQL versions.
is no longer maintained. Please use a .
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
In short, MariaDB 5.1 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.
There are some improvements to DBUG code to make its execution faster when debug is compiled in but not used.
(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 MariaDB 5.1
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.
CVE-2013-1548: MariaDB 5.1.66CVE-2013-1531: MariaDB 5.1.67CVE-2013-0389: MariaDB 5.1.67CVE-2013-0385: MariaDB 5.1.67CVE-2013-0384: MariaDB 5.1.67CVE-2013-0383: MariaDB 5.1.67CVE-2013-0375: MariaDB 5.1.67CVE-2012-5612: MariaDB 5.1.67CVE-2012-5611: MariaDB 5.1.67, MariaDB 5.1.66CVE-2012-5060: MariaDB 5.1.66CVE-2012-4414: MariaDB 5.1.66 CVE-2012-3197: MariaDB 5.1.66CVE-2012-3180: MariaDB 5.1.66CVE-2012-3177: MariaDB 5.1.66CVE-2012-3173: MariaDB 5.1.66CVE-2012-3167: MariaDB 5.1.66CVE-2012-3166: MariaDB 5.1.66CVE-2012-3163: MariaDB 5.1.66CVE-2012-3160: MariaDB 5.1.66CVE-2012-3158: MariaDB 5.1.66CVE-2012-3150: MariaDB 5.1.66CVE-2012-1734: MariaDB 5.1.66CVE-2012-1705: MariaDB 5.1.67CVE-2012-1703: MariaDB 5.1.62CVE-2012-1702: MariaDB 5.1.67CVE-2012-1690: MariaDB 5.1.62CVE-2012-1689: MariaDB 5.1.66CVE-2012-1688: MariaDB 5.1.62: : : :
The following CVEs are also fixed in MariaDB 5.1 but the fix is not tied to a specific version number:
30 Jan 2013
MariaDB 5.1.67
Stable (GA)
29 Nov 2012
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: 01 Feb 2010
See the MariaDB versus MySQL page for a high-level overview of the differences between MariaDB and MySQL.
See the MariaDB 5.1.42 Changelog for a more detailed list of the changes in this release.
MariaDB is kept up to date with the latest MySQL release from the same branch.MariaDB 5.1.42 is based on MySQL 5.1.42 and XtraDB 1.0.6-9.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous release notes and changelogs, the main differences between MariaDB and MySQL are:
For we have merged in all of the upstream changes from MySQL 5.1.42. The have details of what changes were made upstream by MySQL since 5.1.41.
We have included XtraDB 1.0.6-9 in this version of MariaDB. The have details of the changes made to XtraDB since version 1.0.4-8 (the version included with RC).
Thanks to the work of Alex Budovski we have fixed several Microsoft Windows test failures, compiler warnings, and compile errors. We also added page fault counters for SHOW PROFILE on Windows.
We have fixed several Solaris compile issues and warnings and we are now able to offer Solaris binaries for download.
Like we did with our previous releases, various additional changes were made in in our desire to fix warnings and eliminate bugs.
In these included fixing a bug where one connection didn't see newly committed data from another connection and a crashing bug with mysqlslap.exe.
These included removing or fixing invalid tests, cleaning up the codebase where appropriate, and so on.
We are working on setting up a network which will enable us to test and build binaries on many different platforms. We aim to produce binaries in .tar and package formats for all popular platforms. Right now there are generic Linux binaries, packages for Debian and Ubuntu, RHEL/CentOS, and a Windows executable.
The tarball binaries provided in this release are generic binaries, intended for use on most x86-based Linux systems to quickly try out MariaDB without having to compile the source code. For 5.1.38 they were built on Ubuntu 9.04 systems (linked against libc 2.9), for 5.1.39 and later they were built on Ubuntu 8.04 systems (so older libc works). They should hopefully work on most x86-based Linux systems.
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: 09 Sep 2010
For a list of every change made in this release, see the Changelog. For a description of this release see the MariaDB 5.1 overview.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous release notes and changelogs, the main differences between MariaDB and MySQL are:
For we have merged in all of the upstream changes from MySQL 5.1.49. The MySQL release notes have details of what changes were made upstream by MySQL since 5.1.49.
We have included XtraDB from Percona Server 5.1.49-12 in this version of MariaDB.
Like , includes several bug fixes and other improvements. Specific bugs fixed in include:
& FederatedX corrupt ORDER BY with TEXT
Crash in _ma_bitmap_set_full_page_bits on Aria recovery
Some aggregate functions (such as MIN MAX) work incorrectly in subqueries after getting NULL value
RQG: Table corruption after Maria engine recovery - "Wrong data in bitmap"
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: 10 May 2010
MariaDB 5.1.44 b fixes a buffer overflow that might potentially allow an authenticated user to run arbitrary code inside the server. It also has a fix for MySQL Bug #53371: "Security hole with bypassing grants using special path in &#xNAN;db/table names." In all other respects, it is the same as MariaDB 5.1.44.
See the MariaDB 5.1.44 Release Notes for a summary of the differences between MariaDB 5.1.42 and MariaDB 5.1.44.
The most recent release in the is:
| Release Notes | |
Release date: 01 Jun 2010
For a list of every change made in this release, see the .
In most respects will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous and , the main differences between MariaDB and MySQL are:
The most recent release in the is:
| Release Notes | |
Release date: 24 Mar 2010
See the for a more detailed list of the changes in this release.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous and , the main differences between MariaDB and MySQL are:
Bug #613418 (M) aria recovery failure: ma_key_recover.c:981: _ma_apply_redo_index: Assertion `check_page_length == page_length' failed
For MariaDB 5.1.47 we have merged in all of the upstream changes from MySQL 5.1.45, 5.1.46, and 5.1.47. The MySQL 5.1.45,5.1.46, and 5.1.47 release notes have details of what changes were made upstream by MySQL since 5.1.44.
We have included XtraDB 1.0.6-10 in this version of MariaDB. The XtraDB 1.0.6-10 release notes page has details of the changes made to XtraDB since version 1.0.6-9 (the version included since MariaDB 5.1.42).
We have included PBXT 1.0.11 in this version of MariaDB. The PBXT ChangeLog has a list of all of the changes made since PBXT 1.0.09f (the version included in MariaDB since 5.1.41).
Also included is the xtstat program. xtstat can be
used to monitor all internal activity of PBXT.
See xtstat for information on this utility.
Several steps were taken during the development of MariaDB 5.1.47 to improve our Windows builds. Steps included the creation of new Windows build slaves, fixes for Windows compiler errors, and better Windows build automation. Windows builds should now be included with every MariaDB release.
A few Ubuntu-specific fixes are included with MariaDB 5.1.47:
A fix for a dependency problem with Ubuntu 10.04 Lucid packages.
We now build against the full 10.04 release (we used to build against an alpha version of Ubuntu 10.04).
A fix for an Ubuntu issue that appeared when using libmyodbc with mariadb packages.
We've fixed some process issues with the Debian, Ubuntu, and CentOS repositories provided by Open Query. These issues were delaying the latest release from appearing in the repositories. Now releases should show up in the repositories at around the same time a release shows up on the mirrors.
In MariaDB 5.1.47 we've continued to fix bugs and compiler warnings, including bugs in MySQL 5.1.47. The changelog has links to several of the bugs that we have fixed.
We have also continued our work in improving the test suite.
For MariaDB 5.1.44 we have merged in all of the upstream changes from MySQL 5.1.43 and 5.1.44. The MySQL 5.1.43 and 5.1.44 release notes have details of what changes were made upstream by MySQL since 5.1.42.
While preparing for MariaDB 5.1.44 we were made aware of a performance problem with Maria internal temporary tables, compared to MyISAM temporary tables (traditionally used by MySQL). The problem arose because the Maria storage engine has an 8K page size, compared to MyISAM's 1K. With this difference, compacted keys were slower in Maria as we had to search through more data to find a key in each page. After fixing it to use static length keys for most cases, the speed is now in most cases equal or better than MyISAM. This will be permanently fixed for all cases when we add a key directory to Maria storage engine pages.
Like we did with our previous releases, various improvements were made in MariaDB 5.1.44 in our desire to fix warnings and eliminate bugs.
In MariaDB 5.1.44 these included a fix for Bug #534626: "MyISAM table
created in MariaDB not readable by MySQL". With this fix, tables created
without CHECKSUM=1 will be readable by MySQL. We have sent a
patch to Oracle to fix the issue and allow MySQL to read all MyISAM tables withCHECKSUM=1.
Another improvement we made was to not take a mutex when accessing compiled-in plugin code. (The fewer mutexes you take, the better off you are.)
MariaDB 5.1.44 also includes fixes for the following bugs: MySQL Bug #44987,Bug #524025, Bug #524679, Bug #523593, Bug #516148, Bug #520243, and others. See the 5.1.44 Changelog for a detailed list of the various bugs and warnings that were fixed.
We have continued to improve our test suite in MariaDB 5.1.44 to cover additional cases and to eliminate false positives. These included things like adding the ability to send extra commands to the server to setup the environment prior to starting tests, adding new benchmark tests, and fixing some tests that were failing because of time zone issues.
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: 09 Aug 2010
For a list of every change made in this release, see the Changelog.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous release notes and changelogs, the main differences between MariaDB and MySQL are:
For we have merged in all of the upstream changes from MySQL 5.1.48 and 5.1.49. The MySQL , and release notes have details of what changes were made upstream by MySQL since 5.1.47.
We have included XtraDB from Percona Server 5.1.47-11.2 in this version of MariaDB. The page has details of the changes made to XtraDB since version 1.0.6-10 (the version included in ).
In this version of MariaDB we have fixed several recovery and other bugs in the Aria engine. See the for more details and links to the individual bug reports.
An installer for Windows has been included in this version of MariaDB. The installer allows choosing which parts of MariaDB to install (devel headers, client libraries, and etc...), setting the install directory, and optionally installing MariaDB as a Windows service.
The win32 zip file contains both a release and a debug build, and just unzips to a directory. For this reason, the installer is recommended for regular use while the zip file is better for special-purpose installations for power users.
For this release of MariaDB the Release Notes and Changelog are located at the new . Over time, the Knowledgebase will become the primary source of MariaDB documentation and release information. Documentation, Changelogs, Release Notes for previous versions of MariaDB will be migrated here over the next few months. Redirects will be created for items as they are moved from the , so any bookmarks will continue to work after a page has been moved.
The most recent release in the is:
|Release Notes | |
Release date: 5 Dec 2011
is a .In general this means there are no known serious bugs and we believe the code is ready for general usage. A "stable" MariaDB release is equivalent to a MySQL "GA" release.
For a detailed description of see the page.
Compared to , is a bug-fix release.
For a list of every change made in , with links to detailed information on each push, see the .
In most respects will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
The most recent release in the is:
| Release Notes | |
Release date: 15 Nov 2009
See the page for a high-level overview of the differences between MariaDB and MySQL.
5.1.39 Beta is based on 5.1.39 and 1.0.3-8.
MariaDB is 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.
In addition to the differences noted in the , the main differences between MariaDB and MySQL are:
The most recent release in the is:
| Release Notes | |
Release date: 6 Dec 2010
For a list of every change made in this release, see the . For a description of this release see the .
In most respects will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous and , the main differences between MariaDB and MySQL are:
Be notified of new releases automatically by adding the releases rss feed to your favorite feed reader or by subscribing to the announce 'at' mariadb.org announcement list (this is a low traffic, announce-only list).
MariaDB may already be included in your favorite OS distribution. More information can be found on the page.
This release of MariaDB 5.1 includes MySQL 5.1.60.
See the MySQL 5.1.60 Release Notes for a list of changes made upstream in MySQL.
MariaDB 5.1.60 includes from Percona Server 5.1.59-13. See the Percona Server 5.1.59-13 Release Notes for details on what is new in this version of XtraDB.
The Layerjet mirror was recently deactivated. If you were using the Debian or Ubuntu repositories on this mirror, you will need to update your MariaDB sources.list entries to use a different mirror.
If you ever notice the mirror you are using is not responding, check the http://downloads.askmonty.org/mariadb/repositories/sources.list generator for the current list of mirrors.
For MariaDB 5.1.39 we have merged in all of the upstream changes from MySQL 5.1.39. The MySQL 5.1.39 release notes have details of what changes were made upstream by MySQL since 5.1.38.
We have included XtraDB 1.0.3-8 in this version of MariaDB. The XtraDB 1.0.3-8 release notes have details of the changes made to XtraDB since version 1.0.3-6 (the version included with MariaDB 5.1.38).
The FederatedX storage engine replaces the old, not maintained, Federated storage engine.
See also:
Various changes were made in MariaDB 5.1.39 in our desire to fix warnings and eliminate bugs. These included removing invalid tests, removing unused declarations, cleaning up the codebase where appropriate, and so on.
For MariaDB 5.1.39 we have continued our work on improving the test suite. One thing we did was remove unnecessary and confusing 'skipped' messages from mysql-test-run.pl. In mysql-test-run.pl, we auto-generate combinations of replication tests. But this sometimes generates combinations that are meaningless, like running a test that requires row-based replication with statement-based. These superfluous combinations should not be reported as skipped, they should just be deleted. We do keep skip messages resulting from running mysql-test-run.pl in special ways, eg. --mysqld=--binlog-format=statement.
Another thing we did was to remove the ndb suites from the list of default test suites, as we do not support NDB in MariaDB.
We have also done some work on speeding up the test suite. One way we've done
this is to insert
"--disable_query_log ; begin ; ... commit; --enable_query_log"
around all while loops that do inserts.
We've also fixed a race condition in the test system by forcing a restart before maria_showlog_error to get rid of the status from previous connections.
For MariaDB 5.1.39 we switched from using Ubuntu 9.04 and glibc 2.9 for our builds to using Ubuntu 8.04.and glibc 2.7. This should make the binaries more compatible with various Linux systems.
One benefit of our change to using Ubuntu 8.04 and glibc 2.7 for our builds is that we are now able to create CentOS 5 RPM packages. The download page has links to both the individual files and to a CentOS 5 YUM repository.
For MariaDB 5.1.53 we have merged in all of the upstream changes from MySQL 5.1.52 and 5.1.53. The MySQL 5.1.52 and 5.1.53 release notes have details of what changes were made upstream by MySQL since 5.1.51.
We have included XtraDB from Percona-server-5.1.52-11.6 in this version of MariaDB.
For this version of MariaDB we have started building Ubuntu 10.10 "Maverick" and Debian 6 "Squeeze" packages.
Like previous releases, MariaDB 5.1.53 includes several bug fixes and other improvements. Specific bugs fixed in MariaDB 5.1.53 include:
Bug #643463 slow shutdown of XtraDB
A fix from MySQL 5.1.52 for a serious regression: Bug #678047 and MySQL Bug #56821 Windows service cannot start
Various fixes for .deb packaging:
Bug #675185 mysqld_safe hangs spinning at 100% CPU
.debs should link with system libraries, not bundled
PHP compile failure
Upgrade failure on Debian 6 "Squeeze"
and others...
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: 19 Nov 2010
For a list of every change made in this release, see the Changelog. For a description of this release see the MariaDB 5.1 overview.
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous release notes and changelogs, the main differences between MariaDB and MySQL are:
For we have merged in all of the upstream changes from MySQL 5.1.51. The MySQL release notes have details of what changes were made upstream by MySQL since 5.1.50.
We have included XtraDB from Percona-server-5.1.51-12 in this version of MariaDB.
In addition to the static library, libmysqld.a, this version of MariaDB also includes a corresponding shared library, libmysqld.so. This is needed by applications such as Amarok, which use the embedded server from within dynamically loaded plugins or libraries. Details of this are found in , and this patch fixes .
Like , includes several bug fixes and other improvements. Specific bugs fixed in include:
thd->main_da.is_ok() assert in embedded
"ALTER TABLE .. ORDER" does not work with InnoDB and auto_increment keys
Performance regression in 5.1.23/5.1.24
find_shortest_key in sql_select.cc does not consider clustered primary keys
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.
The most recent release in the is:
| Release Notes | |
Release date: 1 Mar 2011
Get notified of new releases automatically by adding the to your favorite feed reader or by to the announce 'at' mariadb.org announcement list (this is a low traffic, announce-only list).
MariaDB may already be included in your favorite OS distribution. More information can be found .
For a list of every change made in , see the . For a high-level description of see the .
In most respects will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
In addition to the differences noted in previous and
MySQL Bug #55656 mysqldump can be slower after MySQL Bug #39653 fix
MySQL Bug #43152 Assertion `bitmap_is_set_all(&table->s->all_set)' failed in handler::ha_reset
MySQL Bug #44797 plugins w/o command-line options have no disabling option in --help
MySQL Bug #53161 Left join optimized into join leads to incorrect results
MySQL Bug #56862 Execution of a query that uses index merge returns a wrong result
MySQL Bug #49600 Server incorrectly processing RIGHT JOIN with constant WHERE clause and no index
MySQL Bug #49322 Server is adding extra NULL row on processing a WHERE clause
MySQL Bug #57024 Serious performance issue with an outer join
Bug #618608 FederatedX is not the default on Windows
Bug #608369 (M) Aria engine recovery failure: "Page: 1 Found wrong page type 0' on CHECK TABLE EXTENDED
Bug #640419 Wrong result with sort_union/index_merge in maria-5.1 and a large table
Bug #634943 "marked as crashed", "zerofilling" and "wrong data in bitmap" when recovering Aria tables
Bug #605798 RQG: Table corruption after Maria engine recovery - "Wrong data in bitmap"
Bug #618558 Assertion data_length < ((block_size) *3 / 4) in write_block_record() at ma_blockrec.c:3483 with --maria-block-size=1K
Bug #634955 ma_blockrec.c:3932: _ma_update_at_original_place: Assertion `blocks->count > 1 || ((new_row->total_length) > (share->base.min_block_length) ? (new_row->total_length) : (share->base.min_block_length)) <= length_on_head_page' on Aria recovery
Bug #643463 slow XtraDB shutdown due to 10 second sleep in purge thread
@@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.
For MariaDB 5.1.55 we have merged in all of the upstream changes from MySQL 5.1.54 and 5.1.55. The MySQL 5.1.54 and 5.1.55 release notes have details of what changes were made upstream by MySQL since 5.1.53.
We have included XtraDB from Percona Server 5.1.54-12.5 in this version of MariaDB. See the Percona Serverrelease notes for what changes were made upstream by Percona.
For this version of MariaDB we are pleased to announce the availability of Debian and Ubuntu repositories that we will keep up-to-date going forward. The new repositories make use of our world-wide network of MariaDB mirrors and will enable hassle-free upgrades to the latest version of MariaDB as soon as it is released.
See for information how to setup your Debian or Ubuntu system to use the new repositories.
As part of the new Debian and Ubuntu repositories we have also . All RPM package releases going forward will be signed.
With this version of MariaDB we are also debuting a new MariaDB downloads website. This new site allows you to filter the various files to show only the ones you are interested in and it will attempt to locate the nearest mirror to you based on your IP address.
Like previous releases, MariaDB 5.1.55 includes several bug fixes and other improvements. Specific bugs fixed in MariaDB 5.1.55 include:
Various storage engine fixes:
Bug #716890 Pre- and post-recovery crash in Aria
Bug #624099 ma_close.c:75: maria_close: Assertion `share->in_trans == 0' failed on UNLOCK TABLES
Bug #700623 Aria recovery: ma_blockrec.c:3930: _ma_update_at_original_place: Assertion `block->org_bitmap_value == ..
Aria table "is marked as crashed and should be repaired"
Queries with "converting HEAP to Aria" status do not respond to KILL QUERY
Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
Various Windows fixes
Fix pbxt crashes on Windows 64 (misalignment on SSE instruction)
mysql_client_test fail on windows x64
merge_debug test fails in Windows debug compilation
maridb crashes in federatedx code
Assertion `table_ref->has_record' failed with small value for join_buffer_size
Elimination of a table results in an invalid execution plan
maria.optimize corrupts stack around alloca() call
Fix sporadic test failures in innodb_mysql.test and partition_innodb_semi_consistent.test
/ Stale data in INFORMATION_SCHEMA.INNODB_LOCKS
and others...
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: 13 Jan 2010
See the MariaDB versus MySQL page for a high-level overview of the differences between MariaDB and MySQL.
See the MariaDB 5.1.41 Changelog for a more detail list of the changes in this release.
This release is a 'release candidate'. This means that we think it's almost ready for a final release but we don't want to call it a final release until more people have had a chance to test it. This release should be followed by a final release in a few weeks.
MariaDB 5.1.41 RC is based on MySQL 5.1.41 and XtraDB 1.0.4-8.
MariaDB is 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.
In addition to the differences noted in the MariaDB and release notes, the main differences between MariaDB and MySQL are:
For we have merged in all of the upstream changes from MySQL 5.1.41. The have details of what changes were made upstream by MySQL since 5.1.39
We have included XtraDB 1.0.4-8 in this version of MariaDB. The have details of the changes made to XtraDB since version 1.0.3-6 (the version included with Beta).
We have included PBXT 1.0.09f RC3 in this version of MariaDB.
This is the 3rd RC release of PBXT. It includes a number of bug fixes (some specifically for MariaDB), and 2 features:
XA/2-Phase commit support
Online backup native driver for PBXT
The backup uses the MySQL backup API (MySQL 6.0/5.4), and is not yet available in MariaDB.
Release notes since the RC2 version in Beta are as follows:
The FederatedX storage engine replaces the old, not maintained, Federated storage engine.
See also:
Like we did with the 5.1.39 Beta, various changes were made in RC in our desire to fix warnings and eliminate bugs. These included removing or fixing invalid tests, cleaning up the codebase where appropriate, and so on.
We are working on setting up a network which will enable us to test and build binaries on many different platforms. We aim to produce binaries in .tar and package formats for all popular platforms. Right now there are generic Linux binaries, packages for Debian and Ubuntu, RHEL/CentOS, and a Windows executable.
The tarball binaries provided in this release are generic binaries, intended for use on most x86-based Linux systems to quickly try out MariaDB without having to compile the source code. For 5.1.38 they were built on Ubuntu 9.04 systems (linked against libc 2.9), for 5.1.39 and 5.1.41 they were built on Ubuntu 8.04 systems (so older libc works). They should hopefully work on most x86-based Linux systems.
------- 1.0.09f RC3 - 2009-11-30
RN291: Fixed bug #489088: On shutdown MySQL reports: [Warning] Plugin 'PBXT' will be forced to shutdown.
RN290: Fixed bug #345524: pbxt does not compile on 64 bit windows. Currently atomic operations are not supported on this platform.
RN286: Fixed a bug introduced in RN281, which could cause an index scan to hang. The original change was to prevent a warning in Valgrind.
RN285: Merged changes required to compile with Drizzle.
RN284: Fixed bug that cause the error "[ERROR] Invalid (old?) table or database name 'mysqld.1'", when running temp_table.test under MariaDB (thanks to Monty for his initial bug fix). Added a fix for partition table names as well.
RN283: Added win_inttypes.h to the distribution. This file is only required for the Windows build.
RN282: Fixed bug #451101: jump or move depends on uninitialised value in myxt_get_key_length
RN281: Fixed bug #451080: Uninitialised memory write in XTDatabaseLog::xlog_append
RN280: Fixed bug #451085: jump or move depends on uninitialised value in my_type_to_string
RN279: Fixed bug #441000: xtstat crashes with segmentation fault on startup if max_pbxt_threads exceeded.
------- 1.0.09e RC3 - 2009-11-20
RN278: Fixed compile error with MySQL 5.1.41.
------- 1.0.09d RC3 - 2009-09-30
RN277: Added r/o flag to pbxt_max_threads server variable (this fix is related to bug #430637)
RN276: Added test case for replication on tables w/o PKs (see bug #430716)
RN275: Fixed bug #430600: 'Failed to read auto-increment value from storage engine' error.
RN274: Fixed bug #431240: This report is public edit xtstat fails if no PBXT table has been created. xtstat now accepts --database=information_schema or --database=pbxt. Depending on this setting PBXT will either use the information_schema.pbxt_statistics or the pbxt.statistics table. If information_schema is used, then the statistics are displayed even when no PBXT table exists. Recovery activity is also displayed, unless pbxt_support_xa=1, in which case MySQL will wait for PBXT recovery to complete before allowing connections.
RN273: Fixed bug #430633: XA_RBDEADLOCK is not returned on XA END after the transacting ended with a deadlock.
RN272: Fixed bug #430596: Backup/restore does not work well even on a basic PBXT table with auto-increment.
------- 1.0.09c RC3 - 2009-09-16
RN271: Windows build update: now you can simply put the pbxt directory under <mysql-root>/storage and build the PBXT engine as a part of the source tree. The engine will be linked statically. Be sure to specify the WITH_PBXT_STORAGE_ENGINE option when running win\configure.js
RN270: Correctly disabled PBMS so that this version now compiles under Windows. If PBMS_ENABLED is defined, PBXT will not compile under Windows becaause of a getpid() call in pbms.h.
------- 1.0.09 RC3 - 2009-09-09
RN269: Implemented online backup. A native online backup driver now performs BACKUP and RESTORE DATABASE operations for PBXT. NOTE: This feature is only supported by MySQL 6.0.9 or later.
RN268: Implemented XA support. PBXT now supports all XA related MySQL statements. The variable pbxt_support_xa determines if XA support is enabled. Note: due to MySQL bug #47134, enabling XA support could lead to a crash.This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL
This page is licensed: CC BY-SA / Gnu FDL