This is the required post about things I observed during this years MySQL conference.

Things that are awesome:

• The tables in sessions. I think these were here last year. They are still awesome this year.
• The new style power plugs. They solved the problem of people tripping over daisy chained power strips and the strips being accidentally turned off.
• Massive quantities of coffee and real cream.

Things that can be improved:

• Lunch tickets. I overheard the same conversation a dozen times about people not being able to find their lunch tickets or not really knowing about them.
• Make badges reversible. A badge under observation will be facing the wrong way.

Things that just bumped me:

• The music is different this year. Now it makes me feel like a teenager struggling with a breakup.

MySQL Sandbox has been updated again. The latest version is 3.0.38, which was just released. There were four releases in the space of one week, and this last one is just a polished edition.

Cherry-picking from the Change log:

• Added option --bind_address to complement the effects of --remote_access;
• The script 'enable_gtid' (for MySQL 5.6 +) now is durable. Previously the changes did not survive a restart.
• Now you can install MariaDB with its bizarre version '10.0'
• It also works well with MySQL 5.7. A bug prevented the creation of 'enable_gtid', but it is

In my ongoing quest to completely understand InnoDB’s data storage, I came across a quite small and inconsequential waste, which is nevertheless fun to write about. I noticed the following block of pages which were allocated very early in the ibdata1 system tablespace but apparently unused (unnecessary lines removed from output):

$ innodb_space -f ibdata1 space-page-type-regions

start       end         count       type                
13          44          32          ALLOCATED           

Background on the doublewrite buffer

Most people using InnoDB have heard of the “doublewrite buffer”—part of InnoDB’s page flushing strategy. The doublewrite buffer is used as a “scratch area” to write (by

I attended the OpenWest Conference in Orem, Utah, and have to say its one of the best community organised conferences. There were over 840+ people at the conference (with more walk-in’s), representing a greater than 100% growth rate compared to last year’s conference.

I gave a talk about MariaDB, and its safe to say that we’ve got many new features that that it’s getting very hard to go in-depth in a span of an hour.

One of the highlights for me was attending talks. I give so many talks, and spend a lot of time talking to people about MariaDB and MySQL, that I very

This afternoon, Arjen Lentz and I were discussing InnoDB’s behavior without a declared PRIMARY KEY, and the topic felt interesting enough and undocumented enough to warrant its own short post.

Background on InnoDB clustered keys

In The physical structure of InnoDB index pages I described how “Everything is an index in InnoDB”. This means that InnoDB must always have a “cluster key” for each table, which is normally the PRIMARY KEY. The manual has this to say in Clustered and Secondary Indexes:

If the table has no PRIMARY KEY or suitable UNIQUE index, InnoDB internally generates a hidden clustered

Sharing my experience of compiling TokuDB + MariaDB 5.5. Why? Because I must have this patch to Sphinx 2.0.4.

Note: I was using what seems to be the "old" method of compiling; quoting Leif Walsh:

... We are looking at deprecating that method of building (MariaDB source plus binary fractal tree handlerton).  It only really needed to be that complex when we were closed source.

I also tried the "new" method of compiling, which I couldn't work out.

Here's how it goes: TokuDB is newly released as open source. As such, it got a lot of attention, many downloads and I hope it will succeed.

However as stable as the

5 years of MySQL

People often write a blog post when they reach some nice anniversary since they joined MySQL community. Well, for those old enough it usually means when they joined MySQL AB as employee. For me this was January 2008. Because I didn't remember the month correctly, I haven't blogged anything then, but decided to save it for a better opportunity - now.

TL;DR Starting this week I will be working for 10gen, selling MongoDB to the Nordics. This blog post is really long - even then it doesn't contain the most interesting stories, I'm not sure if they can ever be published. Sorry for the length, but remember you don't need to read all at once. This is my last MySQL post so save some of it for cold winter days!

2008 - Sun acquisition

read more

Hey everybody!

The Percona Live MySQL Conference and Expo just wrapped up last week and we’re looking to get some conference in review talk from everyone! Talk about your favorite sessions, new things you learned, and your overall opinion of the conference!

Hop online Wednesday at 12:00pm PDT (19:00 GMT) to join the discussion and share your experience from the 2013 Percona Live: MySQL Conference and Expo.

Be sure to watch this twitter search or this blog post get a link for the google hangout tomorrow!

Some talks that were specifically called out:

• Monitoring MySQL with OpenTSDB by Geoffrey Anderson

Today I downloaded Fedora 19 alpha to give it a spin. Some quick notes.

You can get MySQL by asking for the package community-mysql-server. This is 5.5.31. If you ask for stock “mysql” (i.e. yum install mysql-server), you automatically get MariaDB 5.5.30 (mariadb-server).

Fedora 19 runs systemd, so there is no longer /etc/init.d/mysql to start/stop/restart. So just do systemctl enable mysqld.service. Then perform: systemctl start mysqld.service. Replace start with: stop/status too. You can disable it too if you want.

MariaDB 10.0.2 compiles cleanly on Fedora 19 with gcc-4.8. Just perform: yum install bzr gzip tar gcc gcc-c++ make libtool bison ncurses-devel zlib-devel automake autoconf cmake. Get the source code (I just downloaded it). Do BUILD/compile-pentium64-max. Wait. Run make