I just realized that "Flush tables with Read Lock" will not work when a Select query is not yet done.

What happened was there was a runaway query where it was doing a self-join and aggregating the result. The table was about 10 million rows.

When the backup script ran, it issued the flush tables first but since it saw that a select query was still running, the flush table also waited until the query finished which it never did.

In the end, the backup did not work because of the runaway query.

I'm pretty sure that I have read the previous statement in the manual before but it is interesting when an actual warning / caution from the manual actually happens in production.

Want to promote OpenSQL Camp 2008? Use one of the sweet badges shown on this page. A big thank-you to Fixpert for the logo and badges!

There’s a PNG format and a GIF format. To use the badge, download the image, then save it to your server and use the HTML shown below [...]

As I was already up since yesterday 0500 , it was dinner with Sven , Robin and some other conference visitors at a Turkish Buffet place , after which we headed to what seemed to be a great bar where they failed to serve us while waiting for over 10 minutes, so we moved on to another place. and then to be "early"

After walking around a bit in Copenhagen and looking for a bus stop to go to the university I managed to bump into Wim & Co who offered me a ride to the IT University. Where I was almost in time for the first talk by
Jan Wieck about Slony-I, A master to multiple slaves-replication system for PostgreSQL
Given my recent MySQL MultiMaster setups I was fairly interested where PostgreSQL is at today.

Jan started out with explaining where he used replication the most,
For backups and Specialized services so he could offload long running and intrusive reporting tools to an isiolated server.

While …

If I look at Planet MySQL, I see plenty of movement. New projects, new releases of old projects, people trying exciting technologies, others combining old technologies with new platforms. And yet, some of the people who are posting these exciting news are …

Is anyone out there actually still using 32-bit systems for new deployments? On purpose?

I know I occasionally see people who have 64-bit systems and have installed 32-bit OS on them. They are one of two things: people who don’t know what they are doing, or why their server is then having memory problems, or people who have 32-bit Linux installed on their laptops because there is no good 64-bit Flash Player plugin for Linux. (/me shoots Adobe in the Face… it’s called re-compile it and release, please)

The 32-bit laptop people I don’t care about - they are not yet hosting websites on their laptops while browsing YouTube. Yet.

The others just need the learning.

Which brings me back to… should we start to consider 32-bit a dinosaur sort of like AIX 4.1?

(I should be clear here… I am honestly asking… not just trolling. I’m also not advocating bad code - see previous …

I haven’t been doing any new features or exciting things like Query Logging on Drizzle, although I have to say that I’m very much looking forward to logging to syslog. What I have been up to is continuing the seemingly never ending battle to clean up things in the code. Some of the changes are essentially style issues, but some of them additionally help to uncover potential problems. Take my most recent nemesis, ulong.

There are multiple problems with ulong. The first is that it’s non-standard. If you want your code to be portable at all, you have to do something like this in a header file.
#if !defined(HAVE_ULONG) && !defined(__USE_MISC)
typedef unsigned long ulong; /* Short for unsigned long */
#endif
Now, of course, there’s nothing fundamentally wrong with …

I just thought I’d drop a line about our book. Sales appear to be doing well still: the book is still at Amazon sales rank 3,213 and seems to hold pretty steady there. A lot of people have discovered it and are recommending it — including members of MySQL’s professional services team. [...]

I just thought I’d drop a line about our book. Sales appear to be doing well still: the book is still at Amazon sales rank 3,213 and seems to hold pretty steady there. A lot of people have discovered it and are recommending it – including members of MySQL’s professional services team. There are several positive reviews on Amazon (though if you like the book, a few more wouldn’t hurt either).

I have recently added some features to Maatkit’s mk-table-checksum tool that can make it easy to checksum the relevant parts of your data more frequently (i.e. continually, but not continuously). This in turn makes it possible for you to find out much sooner if a replica becomes different from its master, and then you can take action before the differences affect more of your data.

Zembly team has deployed a new application on Zembly called myPicks U.S. Election 2008.

Use this to voice your opinion on the campaign issues being debated in the U.S. Presidential Election - wherever you are in the world.

You can launch the game from: http://zembly.com/mypicksus/

While the frontend is running on Network.Com, the backend including the MySQL server is running on EC2 and data resides on S3

The game is available as a Facebook and MySpace App.

Some cool mashup. They use Dapper to convert some Election related URLs into a API and feed it into the Zembly code/widgets.

Good CloudComputing stuff, check it out!