A while ago I wrote about how to make MySQL replication reliable, part of which is to eliminate temporary tables. The idea is this: if a slave is stopped (or crashed) while a temporary table is open and is then restarted, the temporary table doesn't exist anymore, and the slave will have problems trying to replay any further statements that refer to these tables. Thus, I claimed, there's no alternative but to eliminate temporary tables. This problem may not exist for row-based replication in MySQL 5.1 and later, but most installations I know of are using statement-based replication, even on MySQL 5.1

This is a contentious topic. People love their temporary tables and will ask hopefully "are you sure this isn't safe?" They'll …

There’s been talk over the years of better monitoring for NDB (MySQL Cluster). This has been dubiously named NDB$INFO, after some special magical naming convention for tables holding information on the insides of NDB. Otherwise known as Worklog 3363 (viewable on MySQL Forge).

The basic idea is to get a bunch of things that are already known inside NDB available through a rather standard interface (SQL is preferred).

My top examples are “How much DataMemory is used?” and “Do I need to increase MaxNoOf(Tables|Attributes|ConcurrentTransactions)?”. You can get some of this information now either through the management client (ndb_mgm -e “all report MemoryUsage”) or the …

Thursday, May 29th, at …

So after a ever so temporary but loud moment of insanity[1] having a decision made which I very strongly disagreed with (wanting to release online encrypted backup as closed source), we’re back in the world of freedom and the MySQL Server is (and will be) free and open source software (dual licensed, so you can buy a commercial license of the same thing).

[1] Addition (wanting to remove my use of the word): Marten (rightly) points out that although appreciating the new blog posts, he doesn’t appreciate having his decisions called insanity. He’s right. It’s the wrong way to put it. So, without wanting to censor or change history (instead preferring to illustrate my own stupidity and amazing ability to completely say the wrong thing every 6 months or so), I offer this clarification (that i have tried to express in about 3 drafts of blog posts, none of which have made the light of day as i was never …

I flew back into Sydney on Sunday morning to give a tutorial at Sun’s Expanding Horizon’s summit. It was a half day tutorial on MySQL Cluster - so a shortened version of the one I’ve given at the MySQL User Conference for the past few years. I had about 15 attendees, all of which had done their homework (It probably help that they were pestered via phone :)

The tutorial went really well. It really helps when everybody has done the homework and already have Linux and MySQL Cluster installed. Everybody got up and running (we used mysql-test-run to start a cluster, not writing the config file from scratch, which made things happen a lot faster). Also got some good feedback - yay! We may even have some people look to deploy it after attending, always a plus.

I also gave a “Scaling MySQL” talk that was well attended. I didn’t talk at all about query optimisation, mysqld configuration tuning or stuff like that - instead …

Project: MySQL Forge RSS/Atom feeds

KEY ACCOMPLISHMENTS LAST WEEK

* Already subscribed to MySQL mailing lists (gsoc and internal).
* Contacted my mentor and got instructions about how to set up a local working copy.
* Read documentation about Bazaar, the version control system
* Installed linux (Debian) on my PC, to make a local development environment possible * Started looking at and playing with the source code. * Registered a blog, http://gsoc-forge.blogspot.com/ where I will publish the weekly reports and maybe more. * Installed a local working copy of Forge on my system.

KEY TASKS THAT STALLED LAST WEEK

None....

KEY CONCERNS

My university classes haven't finished yet. Here in The Netherlands we have classes until the end of June. So I have less time available as I …

The next bug-fix release of MySQL Workbench is coming up this week. Tax is still working on the build, we had some unit tests failing that are now passing again. Apart from the usual bug fixes this will be the first release created out of our new Bazaar repositories, http://bazaar-vcs.org/

The team has been relying on the SubVersion source version control system which worked great for us during the last years. But as we did the branching for MySQL Workbench 5.1 we decided that it is time to move to a more advanced system. We have been looking at Mercurial http://www.selenic.com/mercurial/wiki/ but decided to go with Bazaar instead which performed excellent in our tests.

We hope to finish the WB 5.0.22 release by tomorrow and then it will take 24h for the mirrors to catch up.

Key Accomplishments

1. Opened mysql slap and went through the code
2. Read through and attempted a few tutorials http://blogs.techrepublic.com.com/howdoi/?p=133
3. Ran through a few basic tutorials regarding mysql development
4. Learnt about bitclient and the method of committing the patches into the main release.
5. Installed cygwin and obtained the latest 5.1 source distribution.

Key Tasks That stalled last week

• None So far.

Key Concerns

1. Some more documentation or a few tips would definitely help.
2. Also if you are good at database benchmarking , then please do to contact me at taufiqaalam@gmail.com

Tasks in the Upcoming Week

1. Understand the mysql …

Key Accomplishments

1. Opened mysql slap and went through the code
2. Read through and attempted a few tutorials http://blogs.techrepublic.com.com/howdoi/?p=133
3. Ran through a few basic tutorials regarding mysql development
4. Learnt about bitclient and the method of committing the patches into the main release.
5. Installed cygwin and obtained the latest 5.1 source distribution.

Key Tasks That stalled last week

• None So far.

Key Concerns

1. Some more documentation or a few tips would definitely help.
2. Also if you are good at database benchmarking , then please do to contact me at taufiqaalam@gmail.com

Tasks in the Upcoming Week

1. Understand the mysql …

From May 28th-31st, the annual LinuxTag will take place in Berlin, Germany. I followed the growth and evolution of LinuxTag from the very early days and I have fond memories of the event back when it still took place at the University of Kaiserslautern and our SuSE "booth" was just a regular table taken from the lecture rooms...

Things have evolved a lot since then. Today, LinuxTag is one of the largest Linux/Open Source Events in Europe and my new employer Sun is a major sponsor this year. In addition to several talks and keynotes, there will be a large Sun booth in the exhibition area (Booth #205) and we will have a dedicated MySQL demo pod! Some of the things we plan to demo there are the upcoming MySQL Server releases (5.1, …