There was some suggestion after my previous post (Who works on MariaDB and MySQL?) that I look at MariaDB 10.0 – so I have. My working was very simple, in a current MariaDB 10.0 BZR tree (somewhat beyond 10.0.3), I ran the following command:

bzr log -n0 -rtag:mariadb-10.0.0..|egrep '(author|committer): '| \
  sed -e 's/^\s*//; s/committer: //; s/author: //'| \
  sort -u|grep -iv oracle

MariaDB foundation/MontyProgram/SkySQL:

1. Alexander Barkov
2. Alexey Botchkov
3. Daniel Bartholomew
4. Elena Stepanova
5. Igor Babaev
6. Jani Tolonen
7. knielsen
8. Michael Widenius
9. sanja
10. Sergei Golubchik
11. Sergey Petrunya
12. Sergey Vojtovich
13. timour
14. Vladislav Vaintroub …

Looking at the committers/authors of patches in the bzr tree for MariaDB 5.5.31.

Non Oracle Contributors:

1. Alexander Barkov
2. Alexey Botchkov
3. Elena Stepanova
4. Igor Babaev
5. knielsen
6. Michael Widenius
7. sanja
8. Sergei Golubchik
9. Sergey Petrunya
10. timour
11. Vladislav Vaintroub

Oracle (as they pull Oracle changes):

1. Aditya A
2. Akhila Maddukuri
3. Alexander Nozdrin
4. Anirudh Mangipudi
5. Annamalai Gurusami
6. Astha Pareek
7. Balasubramanian Kandasamy
8. Chaithra Gopalareddy
9. Daniel Fischer
10. Gleb Shchepa
11. Harin Vadodaria
12. Hery Ramilison
13. Igor Solodovnikov
14. Inaam Rana
15. Jon Olav Hauglid
16. kevin.lewis
17. Krunal …

I grabbed all the tests introduced in MariaDB 5.5.32 (i.e. “bzr diff -rtag:mariadb-5.5.31..mariadb-5.5.32 mysql-test/” and some foo) and threw them in their own test file. I only kept tests for crashing bugs and ignored those that required plugins (there were two or three, but nothing major). So now I have a test file that should crash MariaDB 5.5.31 and probably before. But, the question is: does this crash Percona Server or MySQL?

While it is excellent to see the MariaDB guys including tests for their crashing bugs, are these MariaDB specific or do they affect other MySQL flavours?

I built a release build of top of trunk Percona Server and ran the test against it. I got no crashes. In a debug build, I got two. One was to do with REPAIR on an ARCHIVE table and the other was “SELECT UNIX_TIMESTAMP(STR_TO_DATE(’2020′,’%Y’));”. I found the same thing for a debug build of top of tree MySQL.

All the other tests …

Recently, we’ve seen a few people ask us about building TokuMX from scratch. While it’s best if you just use the binaries you can get from us (they have all the right optimizations, we’ve tested them, and we can interpret coredumps they generate), we recognize there are other reasons you might need to do a custom build.

Since we actually build six distinct products all using the Fractal Tree indexing® library (community and enterprise versions of TokuDB for MySQL, TokuDB for MariaDB, and TokuMX), our build process is pretty complicated, compared to software packages that might, for example, just involve one source repository and link against a few standard libraries. Our TokuMX builds involve four git repositories, three separate build stages, two different build tools, and …

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.32. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the What is MariaDB 5.5? page in the AskMonty Knowledgebase for general information about the MariaDB 5.5 series.

Download MariaDB 5.5.32

Release Notes Changelog …

This is a followup to my early post a month ago titled: MariaDB replaces MySQL in RHEL 7 (lots of stuff in the comments). It’s clear that MariaDB’s role is in Software Collections, which is new in RHEL.

Steven J. Vaughan-Nichols writes Red Hat will switch from Oracle MySQL to MariaDB, reports.

Sean Michael Kerner has a video (and writeup) with Denise Dumas, RHEL team leader, who talks about Software Collections, MariaDB, and how we’re all friendly …

In my last post, I showed what a Fractal Tree® index is at a high level. Once again, the Fractal Tree index is the data structure inside TokuMX and TokuDB, our MongoDB and MySQL products. One of its strengths is the ability to get high levels of compression on the stored data. In this post, I’ll explain why that is.

At a high level, one can argue that there isn’t anything special about our compression algorithms. We basically do this: we take large chunks of data, use known compression methods (e.g. zlib, lzma, …

The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.3. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the About the MariaDB Java Client page in the AskMonty Knowledgebase for general information about the client.

Download MariaDB Java Client 1.1.3

Release Notes …

My fellow testers and others who run RQG tests on MySQL flavors might be interested in some additions that are being used for MariaDB testing. While none of them is a major breakthrough, maybe they will make somebody’s life a little easier.

RQG Introduction

A quick introduction for those who have never heard of RQG, but are still curious what this blog post is about.

RQG stands for Random Query Generator, also known as randgen — an open-source product, available under the GPL v2 license. Quoting its home page on Launchpad, it is a “pseudo-random data and query generator that can be used to test any Perl DBI, JDBC or ODBC-compatible SQL server, in particular MySQL, but also JavaDB and PostgreSQL”.

The framework was created by my former colleague Philip Stoev, who not only developed a great tool, …

I’m always switching back-and-forth between the 2 different InnoDB flavors in MariaDB – XtraDB+ and the standard InnoDB plugin, so I thought I’d simply post all of the various combinations in a single place. (And then I cover enabling the InnoDB Plugin in MySQL, since it’s an option in 5.1.) [Addition: Thanks to Andrew and Sergei for the tips on shortening plugin-load=. The changes are reflected below.]

Note: Below is for Windows. For Linux, simply change “.dll” to “.so” where appropriate.

MariaDB 10.0:

Do not add anything, as the standard InnoDB plugin is the current default (as of 10.0.3, although I do anticipate this changing in the near future, and I’ll update the post accordingly when that happens).

MariaDB 5.5:

# Enable the 2 below to disable XtraDB+ and enable the standard InnoDB Plugin
ignore_builtin_innodb
plugin-load=ha_innodb.dll

…