A few weekends ago, I started to again look at the code in Drizzle for producing internal temporary tables. Basically, we have a few type of tables:

• Standard
• Temporary (from CREATE TEMPORARY TABLE)
• Temporary (from ALTER TABLE)
• Internal temporary (to help with query execution)

If you’re lucky enough to be creating one of the first three types, you go through an increasingly lovely pile of code that constructs a nice protobuf message about what the table should look like and hands all responsibility over to the storage engine as to how to do that. The basic idea is that Drizzle gets the heck out of the way and lets the storage engine do its thing. This code path looks rather different than what we inherited from MySQL. For a start, we actually have a StorageEngine object rather than just lumping everything into the handler (which we correctly name a Cursor). However… the final …

Until 2.1.1-beta the functions exposed in custom rankers for handling relevancy based on term frequency and Inverse Document Frequency (IDF) did not take field or document lengths into account. In 2.1.1-beta, Sphinx includes functions that take relevance ranking to the next level. New IDF functions mysql> SELECT * FROM myindex WHERE MATCH(‘less_common more_common’) OPTION RANKER= [...]

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.30. This is a bug fix release. See the release notes and changelog for details.

Download MariaDB 5.5.30

Release Notes  Changelog  Overview of 5.5

APT and YUM Repository Configuration …

It’s that time of year again. The annual migration of MySQL users will soon begin! In a little more than one month’s time, much of the MySQL ecosystem will be gathered at the Percona Live: MySQL User Conference and, as usual, you can expect an appearance from the Sphinx Team. Stop by booth 302 to meet [...]

Continuing on from my previous posts, MySQL code size over releases and MariaDB code size I’ve decided to also look into some other code branches. I’ve used the same methodology as my previous few posts: sloccount for C and C++ code only.

There are also other branches around in pretty widespread use (if only within a single company). I grabbed the Google, Facebook and Twitter patches and examined them too, along with Percona Server 5.1 and 5.5.

Continuing on from my previous post, MySQL code size over releases.

I wanted to look at the different branches/patch sets of MySQL out there and work out how far from upstream they deviated. I’m just going to compare against whatever upstream version the most easily accessible version is based on (be it 5.0.x, 5.1.x or whatever).

For MariaDB versions, I removed innodb_plugin and replaced it with xtradb for stats purposes as the MariaDB innodb_plugin is essentially the same as upstream and I don’t want to artificially inflate the diff size.

The first three major versions of MariaDB were all based on MySQL 5.1. I used sloccount and only counted C and C++ code.

So, let’s look at some of the MySQL patch sets/branches that are around. Firstly, let’s look at MariaDB:

After some final testing and polishing, the MariaDB project and Codership are pleased to announce the release of MariaDB Galera Cluster 5.5.29. This is a Stable (GA) release. MariaDB Galera Cluster links:

• Release Notes
• Changelog
• Downloads
• APT and YUM …

First, congratulations Oracle on the GA of MySQL 5.6! Well done!

In this post I walkthrough the features of the first two alpha versions of MariaDB 10.0. The first, 10.0.0-alpha, which was made available in November, and 10.0.1-alpha that saw daylight yesterday. I will go through the features by placing them in the following categories:

• MariaDB 10.0-only Features (features that aren’t in MySQL 5.6)
• MariaDB 10.0 Merged Features (features merged from MySQL 5.6)
• MariaDB 10.0 Reimplemented Features (features reimplemented from features in MySQL 5.6)
• MariaDB 5.x Features now in MySQL 5.6 (features introduced in earlier MariaDB versions which have now been introduced in MySQL 5.6)
• MariaDB 5.x Features Backported from MySQL 5.6 (features introduced in earlier MariaDB versions which were backports of features from MySQL 5.6 development …

I’m getting more and more concerned about the current Oracle approach to MySQL security. And the fact that I was solely responsible for the security@mysql.com for about ten years, doesn’t make it easier, on the contrary, it only emphasizes changes in the attitude.

Starting from the obvious — somewhat slower response to critical bug fixes, which can be expected, Oracle is a big company, right? Very little information about security vulnerabilities is disclosed, CPUs are carefully stripped from anything that might help to understand the problem, it takes hours to map them to code changes. Heck, even test cases are kept private now. This seriously smells …

The MariaDB project is pleased to announce the immediate availability of the following new stable (GA) MariaDB versions:

• MariaDB 5.5.29  — Release Notes, Changelog, Downloads
• MariaDB 5.3.12  — Release Notes, Changelog, …