While updating the mirror last week I was surprised to see that the newest MRU MySQL release is numbered 5.0.79. Previously enterprise releases had even numbers and community releases had odd numbers. I posted the question in #mysql-dev and HarrisonF was kind enough to explain it all.

MySQL 5.0 is running out of version numbers. There are limitations in mysql_get_version(), the executable comment syntax, and other places that mean MySQL can only have two digit release version numbers. MySQL Enterprise has started using odd and even version numbers to extend the life of 5.0.

This raises a few questions. What will happen to 5.0 when it runs out of release numbers? Is community going to be sacrificed to give enterprise more versions to use? Are the version restrictions going to be fixed in the future? For example if a feature is implemented in a community release the executable comment version syntax isn’t suitable for preventing it …

Posted by: Bradley C. Kuszmaul and David Wells

Executive Summary: A MySQL straight join can speed up a query that is very similar to TPC-H Q2 by a factor of 159 on MySQL.

Posted by Bradley C. Kuszmaul and David Wells

Executive Summary: A MySQL straight join can speed up a query that is very similar to TPC-H Q2 by a factor of 159 on MySQL.

Recently, we began looking at TPC-H performance on MySQL. Our early tests yielded unexpectedly poor performance for MyISAM, InnoDB and the Tokutek storage engine. So we decided to take at look at each query individually to see what could be done. This post is about Query 2.

Before going further, let us be clear - this is NOT "TPC-H" benchmarking. The TPC prescribes methods and procedures for measuring performance, and we didn't follow the rules (which you can read at …

Welcome to the 142nd edition of Log Buffer, the weekly review of database blogs.

The SQL Server ’sphere was a busy place this week. On In Recovery… Paul S. Randall posted his latest straw poll, this time looking into your practices around transaction log size management.

Linchi Shea observed, “In a multi-process/multi-thread system, locking is central to maintain data consistency and keep things in order.  . . . [We] need to begin with understanding the locking behavior of the basic building blocks offered by SQL Server . . .  [One] would think that the basic locking behavior …

In a couple of weeks, I will be presenting a session on simple Queuing Models at the free MySQL Camp section of the MySQL User Conference. As luck would have it, I happened to come across a great example today of how a very simple back-of-the-envelope model can help us understand why a system performs the way it does.

My friend and co-worker, Tim Cook, has recently been doing some performance testing with the new Pool-of-Threads scheduler in MySQL 6.0. You can read about the results here and here on his …

Like most people, and with just over a week to go before the conference, I’m putting the finishing touchs on my various presentations.

First up for me, on Monday afternoon, is my tutorial: Scale Up, Scale Out, and High Availability: Solutions and Combinations.

What will be doing?

Very simply: Looking at every potential solution for maximum scalability and availability for your database environment.

If you are attending, be prepared to:

• Expand your mind as we think about scaling up.
• Expand your horizons as we think about scaling out.
• Divide and conquer, as we think about high-availability.

We’re not not hands on in this session – but I will expect you to be brains on!

MySQL does have spatial extensions, and I plan to do some more writing on these in the near future. This is the first blogpost on the subject. The spatial extensions in MySQL looks like what they do in most other databases in terms of overall functionality, but the current implementation leaves a fair bit to be desired when it comes to features and implementation. Spatial extensions include extensions in a bunch of areas:

• Spatial databases. These are datatypes such as point, polygon and geometry etc.
• Spatinal functions. These are functions like distance, size and also functions that check for relations between spatial objects, such as contains and overlaps.
• Spatial indexing. This is typically R-Tree indexes (R for Rectangle) that can be applied when using the Spatial functions above.

Now, all that said, and having said that this support is similar in other RDBMS systems, where is MySQL …

After I wrote about a new feature on MySQL Proxy that helps you read master.info files, I thought that showing an example could come handy.

You can find the complete file on the MySQL Forge and once I have a test case for this script, it will be available on Launchpad.

Explaining the code.
You can see at the top I have

local proto = assert(require("mysql.proto"))

This is important, as it makes the from_masterinfo_string() function available for use.

I also included a function called get_command(), which is a modification of code found …

In a couple of weeks, I will be presenting a session on simple Queuing Models at the free MySQL Camp section of the MySQL User Conference. As luck would have it, I happened to come across a great example today of how a very simple back-of-the-envelope model can help us understand why a system performs the way it does.

My friend and co-worker, Tim Cook, has recently been doing some performance testing with the new Pool-of-Threads scheduler in MySQL 6.0. You can read about the results here and here on his …

In a couple of weeks, I will be presenting a session on simple Queuing Models at the free MySQL Camp section of the MySQL User Conference. As luck would have it, I happened to come across a great example today of how a very simple back-of-the-envelope model can help us understand why a system performs the way it does.

My friend and co-worker, Tim Cook, has recently been doing some performance testing with the new Pool-of-Threads scheduler in MySQL 6.0. You can read about the results here and here on his …

We have finally uploaded the next beta packages of our upcoming database design tool. We have fixed several bugs and added some enhancements that to the Interface. There’s a new editor for defining/maintaining User Defined Datatypes.

There are binary-packages for Windows, Mac OS X Leopard and Linux (Ubuntu and Fedora) as well as the zipped sources for building Workbench yourself. If you experience problems please let us know by filing bugs at http://bugs.mysql.com or contact us directly on via irc-client on irc.freenode.net channel #workbench.
Thank you all for your feedback and contribution. Fetch the new packages at our main download page and give it another try.