Like others we were not satisfied with the fix for a bug in MySQL which caused the query cache and partitioning to not work reliably together. The bug, in simple terms, was that if the query cache was enabled and you used partitioned tables and if a partitioned table was using a transactional engine like InnoDB or XtraDB, the query cache could, under certain circumstances, return incorrect results.

Returning incorrect results is a definite, high-priority bug. However, the upstream fix was to disable all caching of queries from …

So in the summer of 2007 I switched from Windows to OSX which also meant switching from Thinkpad to Macbook Pro. While there were some details I liked on the Macbook Pro, like the at the time quite innovative magnetic design on the lid latch, overall I was sad to not be able to use a Thinkpad. So it also came that my first Macbook Pro had to repaired 3 times in total. Despite having bought the insanely expensive AppleCare this meant having to drop off my laptop for several days (usually 5 business days) or paying an "express service" charge. In general I believe Macbook's to be pretty decent, but not as sturdy as Thinkpads (starting with the availability of spill resistant keyboards). More over they tend to skip on connection options and are overpriced. Then again I really don't care about the price that much. I use my laptop for pretty much everything, from work to DJing to private use. …

This week we present the 100th episode (yes, we started at episode 0), which is part 1 of a 2 part interview with XKCD's Randall Munroe.

OurSQL Podcast history
Episode 0 was on November 26, 2006.
Episode 26 on December 16, 2010 added Sarah Novotny as the first co-host and we hired our audio engineer and producer, Rich Goyette, due to the support of Justin Kestelyn and the Oracle Technology Network.

…

I’ve been updating my (sadly very very neglected, and hacked) blog recently, and along with the new look and feel, have put together a new page for ps_helper (a schema of helper views and procedures for analyzing MySQL’s Performance Schema data):

http://www.markleith.co.uk/ps_helper/

I’ve also updated it with the things that I’ve talked about recently (including my last post on Statement Digests), and put together a couple of version specific scripts, that can be used against 5.5 or the new 5.6 versions.

Each view or procedure now has examples, and their source individually listed too, so that you can see the benefits that you may get from …

A screencast about the MariaDB release process.

(I recommend watching it in full screen 720p, so you can see the details.)

Some links mentioned in the video:

• The MariaDB homepage
• The AskMonty Knowledgebase
• Southeast Linux Fest
• Buildbot
• The MariaDB Buildbot
• The MariaDB Tools project on Launchpad
• The MariaDB Downloads page
• The …

It is not a secret that we’ve been kicking the tires and playing with JIRA for project management. After using it since the beginning of the year most of us like the feel of it and we’ve decided that it makes sense to start using it more.

As you know, the MariaDB project has many fragmented resources. We report bugs in Launchpad. We store our plans in worklog. We’ve never used the Launchpad Blueprint feature for this very reason. We don’t use Launchpad Answers because we have the Knowledgebase.

With this move to hosted JIRA (yes, this is an important link: …

Over the past few days extensive conversations around a new security vulnerability in MariaDB and MySQL have taken place.

It all started as a chain reaction when Monty Program publicly disclosed information about the flaw they had found and about how to make sure your MariaDB and MySQL installations can be fixed. The initial information got assigned the security vulnerabitlity identifier CVE-2012-2122 and the contents can be seen e.g. here http://seclists.org/oss-sec/2012/q2/493.

The bug was found two months ago on April 4th.

Before disclosing the information publicly, given the seriousness of this bug and considering the millions of MySQL and MariaDB installations deployed worldwide, Monty Program informed the biggest distributors of MySQL and MariaDB as a precaution.

On April 6th, Monty Program informed Oracle about it in bug report …

We haven’t posted any Windows benchmarks for a while, and MariaDB for Windows contains some specific improvements which might not be widely know since we haven’t talked much about them yet. This post is an attempt to fix that. We’ll also share current MySQL 5.5 numbers.

My setup is an 8 core 2 socket server (yes, a little bit dated for today, but it is the best machine I have at my disposal), 10K SAS disks with RAID1. I ran sysbench 0.4 single table / 1,000,000 records. I ran the benchmark over a network, with the number of concurrent clients ranging from 4 to 4096.

Here is what OLTP-readonly throughput looks like:

• For most of the tests, MariaDB’s throughput is approx 10% higher than MySQL’s
• For 4096 concurrent clients, MariaDB’s throughput is better than MySQL 5.5 by 476% (2382 vs 413 TPS).

Many people rightfully remark that …

1. Percona Toolkit
Percona Toolkit (aka Maatkit and Aspersa) is must have collection of advanced command-line tools which helps in performing tasks that are too difficult or complex to perform manually.

2. Mydumper
Mydumper is a high-performance multi-threaded backup/restore tool for MySQL. It’s up to 10x faster compared to mysqldump, can take consistent snapshots and provides File compression on-the-fly. Though it’s still under active development but is well tested/used in production on some large installations.

3. MySQL Master HA
This tool helps to maintain your Master-Slave replication setup. A primary objective is automating master fail-over and slave …

We’re quite happy that we’ve released four major releases that are production ready (better known as generally available or GA in the MySQL world) in the last 26 months. That is just a little over two years, and a whole lot of features. In that same time, MySQL has seen one GA release (MySQL 5.5) and we’re all eagerly awaiting the upcoming MySQL 5.6.

You’ll note that we built MariaDB 5.1, 5.2, and 5.3 based on the MySQL 5.1 codebase. A significant number of features went into MariaDB 5.3 (our biggest GA release to date), with the biggest changes in the optimizer in over a decade. There were also many replication based …