I'm really excited about MySQL Cluster. It has a lot of potential to be a good competitor to Oracle RAC, and not just in a copy-cat kind of way.

The thing that makes MySQL different and a good balance, when you're fortunate enough to have the choice, is the "Share nothing" concept. In RAC (and I'm no expert), you use shared storage, usually a Netapp Filer. While filers are seriously cool, they are also seriously expensive, and, no matter how much you gussy it up, it's still a single point of failure.

I was glad I sat in on the Intro to cluster talk at the Users conference, it helped me understand what cluster has to offer, and what it still needs. These needs probably …

MySQL AB today began offering its premium MySQL Enterprise subscriptions through the new Red Hat Exchange (RHX). Designed to simplify the lives of corporate database developers and DBAs, MySQL Enterprise is a comprehensive set of production-tested software, proactive monitoring tools, and support services.

I just saw the review on Slashdot about the Visibone cards:
http://books.slashdot.org/article.pl?sid=07/05/09/1331253&from=rss

At the MySQL User's Conference I gave a few of these out. They were of nice quality and were well laid out with information.

The only thing that surprised me about them, was that I had not realized that we had that much SQL syntax :)

Here are the instructions for building mod_jk.

1. Download the source and untar it.

2. Ensure you have Sun Studio compiler in your PATH followed by /usr/ccs/bin. Save the following in 'make_solaris.sh' in the 'native' directory :

#!/bin/sh
INSTALLDIR=/opt/coolstack
APACHEDIR=$INSTALLDIR/apache2
make distclean
PATH=$INSTALLDIR/bin:$PATH
export PATH
./configure --with-apxs=/opt/coolstack/apache2/bin/apxs --with-java-home=/usr/java --with-prefix=$INSTALLDIR
make
make install

3. Go to the 'native' directory and run ./make_solaris.sh

4. Edit your httpd.conf file to include :

  LoadModule jk_module        modules/mod_jk.so

5. Restart the apache httpd server.

Let me know if this …

IBM and Red Hat collaborate on Linux-on-Mainframe. JasperSoft launches updated products. Black Duck debuts new product for software M&A. (and more)

IBM and Red Hat Announce Worldwide Enterprise Linux-On-Mainframe Program, IBM / Red Hat (Press Release)

JasperSoft Launches JasperReports Professional Edition, JasperReports Developer Edition, and JasperStudio Professional Edition, JasperSoft (Press Release)

Black Duck Furthers Technology Leadership with transactIP for Software Code Review Ahead of Mergers and Acquisitions, Black Duck Software (Press Release)

…

There are a lot of MySQL udf's floating around, but there are not a lot of resources to just site down and write a UDF.

For this reason I put up a skeleton project for UDFs:
http://hg.tangent.org/skeleton-mysql-udf

You are welcome to pull it and make use of it for your own projects. Its a very simple design and could use a few more people contributing to it.

It does though handle all of the make/build environment for you, which is pretty nifty :)

My recoup cost for this is one cup of Green Tea from the Victrola here in Seattle.

From the Oracle TechBlogs:

The Falcon Has Landed

You can check out the camera they have setup as well:
http://pressroom.oracle.com/falconcam.jsp

When I first saw the headline, I wondered if Oracle was as excited as MySQL is to see new releases of our Falcon Storage Engine!

Oh well, their falcons are still cute!

I had the interesting customer case today which made me to do a bit research on the problem.

You can create merge table over MyISAM tables which contain primary key and global uniqueness would not be enforced in this case, this is as far as most people will think about it. In fact however it is worse than that - if you have same key values in underlying base tables some of the queries may give you wrong results:

PLAIN TEXT SQL:

1. mysql> CREATE TABLE t1(id int UNSIGNED PRIMARY KEY);
2. Query OK, 0 rows affected (0.07 sec)
3.  
4. mysql> CREATE TABLE t2(id int UNSIGNED PRIMARY KEY);
5. Query OK, 0 rows affected (0.02 sec)
6.  
7. mysql> CREATE TABLE tm(id int UNSIGNED NOT NULL PRIMARY KEY) type=merge union(t1,t2);
8. Query OK, 0 rows affected, 1 warning (0.03 sec)
9.  
10. mysql> INSERT INTO t1 …

You might have noticed that MySQL is hiring. We need more people. Last time I looked, we had 29 open positions, nearly all of which worldwide.

Internally, we have an initiative to come up with a canonised list of “The Top Reasons To Work for MySQL“. This is my input to the internal group of people compiling that list:

1. You get to work with some of the smartest people on the planet, as users, customers and colleagues.
2. You don’t have to relocate, but you can, if you (or your spouse) want to.
3. You usually work from home and can be available for family emergencies.
4. You can influence your own daily working rhythm.
5. You get to travel, meet …

Today seems to be Innodb day in our Blog, but well this is the question which pops ups quite frequently in Innodb talks and during consulting engagements.

It is well known to get better performance you should normally set innodb_log_file_size large. We however usually recommend caution as it may significantly increase recovery time if Innodb needs to do crash recovery.

I'm often something like what recovery time would expect for 512MB total log file size. This is however question with no exact answer as there are many things which affect recovery time.

For example Paul mentioned YouTube has something like 4 hours recovery time even if logs are of reasonable size and wikipedia has 40 minutes or so with innodb_log_file_size=256MB. In other cases I know same log file time may have recovery time of 5-10 minutes.

To understand things affecting recovery time you better to understand how Innodb recovery …