If you’re trying to email anyone at @askmonty.org or @montyprogram.com, you’ll notice that you’re getting a bounce. No, we’ve not disappeared from the face of the earth – we’re just having issues with our ISP. We’re still writing code to make MariaDB better, we even managed to sneak in a release of MariaDB (yes, 5.2 is now released – download 5.2.3 now!)
We’ll keep you updated on the situation as our ISP fixes the problem.
Update: 12/11/2010, 8.15am UTC – email services are back up. If you tried sending us stuff in the last few days, don’t hesitate to resend it.
Recently I tested our new segmented key cache feature for MyISAM in MariaDB 5.2.2-gamma for performance gains. You can check our new features in MariaDB 5.2 in our Ask Monty Knowledge Base
You will also find the details about the segmented key cache feature in our Knowledge Base at:
We wrote a test in LUA for SysBench v0.5 called select_random_points.lua, to figure out the performance gain of splitting the key cache’s global mutex into several mutex under multi user load. Read more
There was quite a rush for the t-shirts and we have our three winners:
Due to your high interest in our Istanbul2010 t-shirts, we are extending our giveaway quiz until November 30th.
Question: What is Maria in MariaDB and how is it connected to My and Max?
Email your answers to “istanbul2010-contest [at] askmonty (dot) o r g” before 30 Nov 2010. Good luck!
By the way, the design on the t-shirts looks like this:
Monty Program along with various guests and our friends at the recently founded SkySQL recently wrapped up a meeting in Istanbul Turkey. Sadly it rained most days but we had a good time and got a lot done.
Besides learning how to say “Şerefe” which is “Cheers” in Turkish, we discussed the future of MariaDB, our companies goals, the MariaDB knowledge base and many other topics. Since I am the web guy, I lead the presentation / talk on the KB and thought I would share some highpoints of it with you.
We saved three XL-sized t-shirts from our recent all-company meeting in Istanbul. At first we thought it would be a good idea to give away the shirts through a random drawing. But after mulling it around in our minds for a day or two, we thought we should make it a bit more fun, so we decided to have a small quiz (don’t worry, it’s only one easy question).
Before we get to that, here’s a run-down of what we did in Istanbul. Our community and documentation guys (Daniel Bartholomew, Colin Charles, and Kurt von Finck) had the great idea to create an “Istanbul Haber” (aka Istanbul newspaper) for each day of the meeting. Read more
OpenSQLCamp Boston 2010 happens 16-17 October 2010, at MIT in Boston (there is an evening social session on Friday the 15th as well). Its organised by MySQL community aficionado Sheeri Cabral, and by looking at the schedule and sponsors, it is going to be one of the most diverse OpenSQLCamp’s by far.
Monty Program is a sponsor, and I (Colin) will be participating on behalf of Monty Program to bring some information about what’s new from the Istanbul company meeting. More of the company certainly wanted to be at the event, but most are going to be spending some quality vacation time in Istanbul, since our all company meeting only ends on the 12th.
There are more sites out there that have their backends running MariaDB. In fact, as we work to get it recommended alongside its upstream provider, it seemed time to have “Powered by MariaDB” logos. Check out the badges that Daniel created. Feel free to copy the images or hotlink them from the server.
As an aside, would any readers be interested in purchasing t-shirts or other MariaDB merchandise? What merchandise should we make, besides just stickers?
The intention from the start was to make upgrades to newer MySQL versions trivial. We have done a lot of work to keep data formats compatible (both in the .frm files and in the storage engines); when you install a new version of MySQL things should “just work”.
For a long time this was true, until MySQL 5.0 where we had to do some data incompatible changes, like in the way some characters were sorted and how end-of-line blanks were stored in indexes.
To make the upgrade process easy, we created the ‘mysql_upgrade’ program which should detect possible incompatible tables and automatically convert data as needed. Read more