I've just improved innotop substantially, and released version 0.1.106 (download innotop from the original article), and I'm also preparing a series of articles on how to use it for real, practical things. I'd like to know what you think of it, what problems you have, what features you want. It would be a huge help if you'd start it, toggle through its modes, and give me your feedback.

MySQL doesn't yet provide good tools for some troubleshooting tasks. Fortunately, there is some low-hanging fruit you can pluck. One example is a tool to record who owns a MySQL database connection, so long-running transactions can be traced back to the source. This article demonstrates an easy way to solve that problem.

While most of the code in MySQL is written by employees of MySQL, we are open to contributions by companies and individual contributors. In an attempt to make it easier to contribute to MySQL, we have created the MySQL Code Contribution Program.

MySQL Forge is a collection of projects based on MySQL. The Code Contribution Program is one step beyond that: It’s for code that goes directly into the MySQL-owned and managed code base.

As such, MySQL has accepted contributions before. Through the Contributor License Agreement (now released as beta), we have streamlined the legal aspect of the process.

Beside the legal side of the contributor program, there is the development aspect. Contributors may need help and guidance from MySQL developers. …

OK, so OSCON is one of, if not the, largest open source conference in the world. The complete list of sessions and tutorials is staggering. So, for those of you Sakila fans heading out to Portland for the "big gig" next week, I figured I would highlight the MySQL sessions and tutorials and also give my top 6 picks of the sessions you simply shouldn't miss.

MySQL Related

• Monday has both my own "Maximum Velocity MySQL" (on performance tuning and coding) and Brian's "MySQL 5.1 In-Depth" tutorials. Note that Brian is also giving …

I’ve just improved innotop substantially, and released version 0.1.106, and I’m also preparing a series of articles on how to use it for real, practical things. I’d like to know what you think of it, what problems you have, what features you want. It would be a huge help if you’d start it, toggle through its modes, and give me your feedback. Enhancements in version 0.1.106 include: InnoDBParser is much more complete and accurate.

MySQL doesn’t yet provide good tools for some troubleshooting tasks. Fortunately, there is some low-hanging fruit you can pluck. One example is a tool to record who owns a MySQL database connection, so long-running transactions can be traced back to the source. This article demonstrates an easy way to solve that problem. Introduction One of the reasons I wrote the innotop InnoDB and MySQL monitor was to monitor long-running transactions.

One of the most common commands that a MySQL DBA performs is the SHOW FULL PROCESSLIST command. I can't tell you how many thousands of times I've run this. The problem is that there is too much information that I need to filter out before I can focus on the queries that matter. Fore xample, I don't want to see any idle connections nor do I want to see my own connection. The other problem is that if most queries run in under a second, I miss a lot of queries.

Problem solved!

I have posted a very handy script named proclist.pl to MySQL Forge.This script can be used to periodically poll the server for queries, with millisecond precision. Moreover, the output can be imported into a MySQL database for further analysis.

I came across as interesting situation with MySQL that I had not come across before. Most people would not have come across this problem either as the majority of MySQL installs are either single server based. If there are multiple servers, then they are usually the same platform or very close eg. Linux on x86 etc.

The issue I came across was actually in respect to a MySQL Forums entry and this guy who was trying to replicate from Unix to Mac OS X. The problem was explained that the replication showed the status as normal, the read_master_pos_log and the exec_master_pos_log were all fine, and the relay logs were working. There was no errors showing and the replication seemed to be going through according to all system status reports. The issue was that no data was going in to the tables.

read more

I came across as interesting situation with MySQL that I had not come across before. Most people would not have come across this problem either as the majority of MySQL installs are either single server based. If there are multiple servers, then they are usually the same platform or very close eg. Linux on x86 etc.

The issue I came across was actually in respect to a MySQL Forums entry and this guy who was trying to replicate from Unix to Mac OS X. The problem was explained that the replication showed the status as normal, the read_master_pos_log and the exec_master_pos_log were all fine, and the relay logs were working. There was no errors showing and the replication seemed to be going through according to all system status reports. The issue was that no data was going in to the tables.

read more