Just saw a brief “this is how it’s currently working” on Martin’s implementation of the SQL frontend to the NDB$INFO work.

It’s awesome.

You only get one chance to make a first impression. I would think the following tips would be common sense, yet I am surprised every day.When on a phone interview, don't put the interviewer on hold.I don't mind calling you on your cell, but if the call drops, you're done.I know you might be nervous, but don't cut me off in mid-sentence.When you take my call, don't be driving in a car.I don't

More and more people are lending advice to the MySQL guys at Sun (not even mentioning the level of fact based slapping its getting along the way). I think there is one important thing missing in this advice, Sun has its feet in 3 RDBMS products: MySQL, Drizzle and PostgreSQL. Even if they paid a 1B USD for the first, the other two are important to remember as well. Actually Drizzle is mentioned a lot in this advice, but PostgreSQL is oddly absent. IMHO MySQL serves a market quite perfectly at this point and I do not see this changing in the next few years.

There are annoyances all around, but the fact of the matter is that we know them well and they do not stop us from …

In case you were wondering, after seeing this self-defined tutorial, backing up MySQL 5.1 partitioned tables does not require any particular additional technology.
This tutorial presents MySQL 5.1 in a short paragraph, and then starts talking about a commercial backup application, as if it were the only way of backing up partitioned tables.
The title, for sure, is misleading. Backing Up MySQL Partitioned Tables. Reading such a title, readers expect either a list of possible solutions, or being presented with the only existing way of dealing with this task. Instead, the only instructions that you get is how to use the above mentioned tool, which is definitely not the only way of getting the job done. It is also doubly misleading because, since partitioning is a new technology, the casual reader may think "oh? What's peculiar with …

I have been using libumem and LD_PRELOAD to track down memory allocation problems in a lot of applications over the years, and I just love the runtime linker on Solaris (AFAIK you will find some of the features on Linux as well). The fact that I can load other libraries that replace or add functionality of the program is just great. If you haven't read it already I would encourage you to read the man page for ld.so.1. If you are a developer using Solaris and haven't used libumem to hunt down memory bugs, you should read this blog by Adam Leventhal.

Last week I spent an evening …

The Monolith Toolkit of scripts for DBA routines. 0.4.3 has been released. You can download it here: http://code.google.com/p/monolith-toolkit/

Some information on the toolkit and what it contains:

• mt-backup-parallel -> runs mysql backups in parallel super fast, has lots of reporting features
• mt-check-replication -> script to report on replication status for slave servers
• mt-rhcluster-check-filesystems -> reports on redhat cluster filesystems (for mysql active/passive clustering)
• mt-rhcluster-script-wrapper -> wrapper script for running any of these scripts on a redhat cluster, chooses the active node to run the script on
• mt-connections-log -> logs connections to mysql to disk, reports on threshold overages
• mt-flush-tables-sequence -> runs through schema.tables to flush in …

After getting sysbench running properly with a scalable memory allocator (see last post), I can now return to what I was originally testing - what memory allocator is best for the 5.1 server (mysqld).

This stems out of studies I have made of some patches that have been released by Google. You can read about the work Google has been doing here.

I decided I wanted to test a number of configurations based on the MySQL community source, 5.1.28-rc, namely:

• The baseline - no Google SMP patch, default memory allocator (5.1.28-rc)
• With Google SMP patch, mem0pool enabled, no custom malloc (pool)
• With Google SMP patch, mem0pool enabled, linked with mtmalloc (pool-mtmalloc)
• With Google SMP patch, mem0pool disabled, linked with tcmalloc (TCMalloc)
• With Google SMP patch, mem0pool …

Hey,

Today, NetBeans Team announcing a joint effort between NetBeans and strategic partner ICEsoft to offer support for Woodstock users. With the latest ICEfaces-NetBeans Plugin, Woodstock users will be able to migrate and maintain their existing projects, and ICEfaces has provided a detailed porting guide to explain the process.

For more details and resources, check out this News Item;

http://www.netbeans.org/servlets/NewsItemView?newsItemID=1324

Happy NetBeaning!

ZRM 2.1: Backing Up MySQL Partitioned Tables

MySQL 5.1 is generally available for production use. One of the key features of MySQL 5.1 is partitioning. This how to shows how to install and configure Zmanda Recovery Manager for MySQL (ZRM) 2.1 to perform backup and recovery of MySQL partitioned tables.

Lenz Grimmer and Duleepa Wijayawardhana have made a series of interviews with the everyday heroes of MySQL. Some are oldtimers, others are new. Some previously worked for MySQL AB, others joined our team through Sun. But all are part of the fabric of today’s MySQL.

Lenz and Dups asked a number of interesting questions from these guys:

• Lars Heill, Release Engineering Manager
• Masood Mortazavi, MySQL …