If you are upgrading from 5.0, please review the upgrade information first before diving in.

The packages take care of backward compatibility with the older .so.15 client library (5.1 has .so.16), including on CentOS 5 (no separate “compat” RPM required).

This release for the first time also has packages (in YUM repo) for RHEL/CentOS 5. The MariaDB RPMs should purposely conflict with any 5.0, as well as any 5.1 of different origin, so that you consciously have to choose to upgrade and won’t accidentally end up for instance automatically upgrading from 5.0 to 5.1. We say should because while we tested various scenarios, the real world is bound to teach us more. Just be cautious, and please file bugs if you spot anything weird.

We didn’t build RHEL/CentOS 4 RPMs, because it originally came with MySQL 4.1 which is ancient, this means that other packages on that system have a dependency on libmysqlclient.so.14. If you do have a need for RHEL 4 packages, please let us know.

Generic Linux binary tarballs and the base source tarball to create all builds are also available, although to recreate one of the packages it’s easiest to use the relevant source package.

Please enjoy, and if you encounter any problems, file bugs with OurDelta or MariaDB on Launchpad.

If you’d like to keep up to date about MariaDB developments, there is a Planet MariaDB. If you have a feed relevant for MariaDB, you can submit it through the site.

Monty has merged/rewritten the microslow patch, so (most of) the detail/filtering you’ve become used to from the 5.0 OurDelta builds are there. All the Percona InnoDB patches are of course in the XtraDB plugin.

For Debian/Ubuntu, you will find a nice baseline my.cnf that, among other sane settings, defaults to InnoDB and strict mode by default – just like the Windows config wizard has done for a few years already.

The GRAPH computation engine didn’t quite make this build, but if you’d like us to build the plugin library for you for any of these distros/architectures, just ask. For DIY, you can just grab the exact source tarball we used to build the MariaDB packages, compile the plugin against it from the launchpad repo and copy the .so library to the plugin directory. Instructions are in the docs and the engine/INSTALL file.

Lots more to tell, but that would make it not be a quick overview 😉

Please enjoy, and if you encounter any problems, file bugs with OurDelta or MariaDB. Don’t worry about picking the right project, if you get it wrong Launchpad lets us toss it across, and some bugs actually require fixes on both ends so they get attached to both!

If you’d like to keep up to date about MariaDB developments, there is a Planet MariaDB. If you create a feed relevant for MariaDB, you can submit it through the site.