Just follow our very simple installation instructions.

(note: give the mirrors some hours to sync up)

Quick overview

• See the Release Notes for relevant bugfixes.
• Drop-in replacement for stock MySQL 5.0 or 5.1 (If you’re coming from stock MySQL, see the MariaDB extras/differences overview).
• 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.

• Debian: Etch (4), Lenny (5)
• Ubuntu: Hardy (8.04), Intrepid (8.10), Jaunty (9.04), Karmic (9.10)
• RHEL/CentOS: 4, 5
• Binary tarballs: generic Linux, built on Ubuntu Hardy

Quick overview

• For MariaDB we use different repository directories to ensure that you can’t accidentally upgrade or revert major versions without you explicitly choosing to do so.
• At this point we have Ubuntu Hardy, Intrepid, Jaunty and Karmic for you, as well as Debian 4 (Lenny). Etch (Debian 4) is waiting on a small fix (thanks to Antony Curtis for helping with that).
• The package names start with mariadb*, except for mysql-common which has a hard dependency elsewhere in the Debian/Ubuntu environment.
• The binaries and directories are generally called mysql* although there are some Maria engine command line tools as well.
• Apart from possible build glitches and bugs, this is a drop-in replacement for stock MySQL 5.1
• 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)
• MariaDB includes these new/replacement storage engines: XtraDB (the enhanced InnoDB plugin, by Percona) and PBXT (by Primebase Technologies).
• 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.

• Binaries: http://master.ourdelta.org/bin/
  32 and 64-bit Linux tarballs
  32 and 64-bit OSX tarballs and DMGs
  
• Source tarball: http://master.ourdelta.org/src/

For the GRAPH Engine documentation, see http://openquery.com/graph/doc. It’s not another general purpose engine, it’s a computation engine. Different beast altogether, but darn useful!

Since it’s new code, it’s only in the -Sail patchset (bleeding edge).

If you already installed the OurDelta repository information, yum update or apt-get upgrade will install the updated packages for you. Please do review the special notes on backward compatibility below.

Fixes & Additions:

• Fixed up all backward compatibility and reserved keyword issues. You can now drop in an OurDelta build to replace a stock version. Generally this merely involved some minor changes to various patches; however Arjen worked on the MicroSlow patch so that it now accepts and returns fractional seconds. This makes it backward compatible with the stock MySQL. Percona has indicated it will also move to this new version of the patch.
• Note: if you are upgrading from the OurDelta 5.0.67.d6 build, or any of the earlier Percona builds, you will need to adjust your long_query_time from microseconds to fractional seconds. (This should be the only time we needed to do this, e.g. break something to unbreak things
• Added Mirrored Binlog and Fast Master Promotion patches (by Google, extracted by Percona).
• Added KILL IF IDLE and InnoDB Freeze patches (by Google, extracted by David Stainton, Spinn3r), now in a public build for the very first time!
• Added updated “innodb_rw_locks” patch (by Yasufumi Kinoshita); only in -Sail binary.
• Added new “adaptive flush of InnoDB buffer pool” patch (by Percona); only in -Sail binary.
• Bugfix “variables out-of-bounds on 32-bit” aka BIG_TABLES (launchpad#284123, mysqlbug#35346) by Antony Curtis.
• Bugfix “mysqld_safe open_files_limit” (launchpad#290190, mysqlbug#40368) by Erik Ljungstrom.
• Improved build process: creating patched source tarballs once, then feeding these into the various build machines. This means we now have those same source tarballs also available for you to download, just in case you wish to build them for another platform! Lots of script magic and time by Peter Lieverdink.
• All distro packages now also have the appropriate source packages available.
• Ubuntu 8.10 (Intrepid) builds added.
• RHEL/CentOS release RPM: further simplifies setup for YUM, with automatic mirrors and GPG key. Thanks Steve Walsh for that contribution!
• More documentation for each feature so that you know exactly which new configuration options and SQL commands you get, and how they work.
• All pages on the website now accept comments, so it’s even easier to provide corrections and other feedback on specific content pages and posts. Not intended for reporting bugs.

Your interest (from 53 different countries according to Google Analytics!) and response has been great! Among the feedback, saw a few bug reports on minor issues in the packaging, most of which have already been addressed for the next build (bug handling progress is all visible on Launchpad). And discussion about various patches that are “around”; some mails came to people directly but we try to encourage using the oursql-developers team mailing list.

• RHEL/CentOS 4.6/5.2 RPMs and YUM repo info
• Ubuntu Hardy DEBs and apt-get repo info

Other useful links:

• Launchpad project and patch repo
• Developer team and mailing list (do join!)
• Bug handling

Now, this being a first release into the wild, there are bound to be some glitches. Most likely in the packaging (and the repo instructions) but possibly also in the builds themselves. Trust comes over time, right? That’s ok, you can help! Simply report any issue using the above bugs link! And please do report success also, although that’s done best through the mailing list or a blog.

In case you’re wondering, 5.1 and beyond are also coming, with more interesting goodies! And you can help! Your first step is to join the mailing list.

A big thanks to everybody involved so far, this was a great team effort! (see the about page for a non-exhaustive list)