The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-14. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 5.1.44 Release Notes

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: 24 Mar 2010

See the MariaDB 5.1.44 Changelog 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 release notes and changelogs, the main differences between MariaDB and MySQL are:

Contents

  1. Includes MySQL 5.1.44
  2. Performance Improvements
  3. Fewer warnings and bugs
  4. Test Suite Improvements

Includes MySQL 5.1.44

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.

Performance Improvements

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.

Fewer warnings and bugs

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 with CHECKSUM=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.

Test Suite Improvements

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.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.