I work on many MySQL performance problems. This gives me many ideas on how to improve monitoring. Sometimes the ideas are good and now is the time to share those requests with MySQL devel because they are getting a lot of work done (and filling my inbox with updates). My latest requests are listed below and likely to appear in a Facebook patch real soon:

• Make the Rows_examined field in the slow query log valid for insert, update and delete statements. MySQL devel just fixed this for bug 49756.
• Use the Lock_time field in the slow query log for per-statement row lock wait times. See feature request 53496
• Count queries by success and failure. The counter names could be Queries_ok and Queries_error. They are incremented when a command or query finishes without or …

It’s Friday already, and we know what that means! Log Buffer, the industry’s weekly review of database blogs is here again for your reading pleasure in the 188th issue.

Starting off this week’s issue is a request from Mark Grennan a DBA who would like to let the community know about his blog MySQL Fan Boy, where he wrote an interesting post on including a script to replace MySQL table files on a live system, making it faster and limiting locking on large table loads. Also a post this week on whether MariaDB is a drop in …

Ronald asked me if I could present at ODTUG’s Kaleidoscope conference, which is only a couple hours from me, but I’ll be at the Netways OSDC that week. Matt Yonkovit will be there representing Percona. I wish I could go: I would really like to mingle with more Oracle users and developers, and I think that participation is the key to building relationships between MySQL and Oracle users — two groups of people who are going to be overlapping more in the future. If you can attend, I hope you will — and blog about it so I can read.

Related posts:

1. OpenSQL Camp events in 2009 There are
2. …

The Beacon Pattern:
- This is a “Get out of the business” pattern
- Identify an oft-occurring and annoying task
- Automate and document it to the point of being able to hand it off to someone far less technical

Example:
- System admins were being put in charge of scheduling rooms in the building
- They wrote a PHP web application to help them automate the task
- They refined the app, documented how to use it, and handed it off to a secretary
- They have to maintain the app, but it’s far less work.

The Community Pattern:

- Prior to launch of a new service, create user documentation for it.
- Point a few early adopters at the documentation and see if they can use the service with minimal support
- Use feedback to improve documentation, and the service
- Upon launch, create a mailing list, forum, IRC channel, or Jabber chat room and ask early …

Dear Community,

Percona Server 5.0.90, release 21 is available for use.

Comparing to the previous release it has following new features:

• The build is based on MySQL-5.0.90

Fixed bugs:

• Fixed Bug #539190 Percona-XtraDB package doesn't allow libmysqlclient15off
• Fixed Bug #479106 mysql-5.0.87 + patches-5.0.86 compile fail in ubuntu 9.10 (karmic)
• Fixed tests mysql, mysql_upgrade, ssl*

See release notes for earlier changes.

RPMs and DEB packages are available in Percona repository.

I am attending the Professional IT Community Conference – it is put on by the League of Professional System Administrators (LOPSA), and is a 2-day community conference. There are technical and “soft” topics — the audience is system administrators. While technical topics such as Essential IPv6 for Linux Administrators are not essential for my job, many of the “soft” topics are directly applicable and relevant to DBAs too. (I am speaking on How to Stop Hating MySQL tomorrow.)

So I am in Seeking Senior and Beyond: The Tech Skills That Get You Promoted. The first part talks about the definition of what it …

We are pleased to announce the availability of the 1.0.5 release of InfiniDB Community Edition.  This is the third of our monthly maintenance releases that are scheduled throughout the spring.

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.  You can download the latest InfiniDB binaries, source code, and updated documentation at: ht...

The ODTUG is an independent group of very skilled Oracle users, fond of high level training, specifically in matters of development tools. This year, after the Sun acquisition was finalized, the ODTUG board of directors asked the MySQL community to provide some contents for their conference, …

update on latest accomplishments:

1. added support for filters (compare engine_condition_pushdown) on non-root operations, this in 2 flavors:
   
   • - constant/immediate filters that is provided after NdbQuery has been defined, these may not contains filter conditions referencing other NdbQueryOperation's,
   • - parameterized/linked filters, these type of programs must be provided when building the NdbQuery-object.
   
   The constant filters should be "easy" to integrate with ndbapi/mysqld, but the parameterized/linked is harder as we need to add new features to NdbScanFilter.
   
   Once this is integrated into mysqld, it will provide better performance for already pushable queries, see page 43 in my UC presentation (ref: filter).
   
   
2. added support for NdbQueryOpertation's referencing non-direct parent …

MySQL 5.1 introduces row based binary logging.  In fact, the default binary logging format in GA versions of MySQL 5.1 is 'MIXED' STATEMENT*;   The binlog_format  variable can still be changed per sessions which means it is possible that some of your binary log entries will be written in a row-based fashion instead of the actual statement which changed data, even when the global setting on the master is to write binary logs in statement mode.   The row-based format does offer advantages particularly if triggers or stored procedures are used, or if non deterministic functions like RAND() are used in DML statements.

A statement based replication slave can get out of sync with the master fairly easily, especially if data is changed on the slave.   It is possible for a statement to execute successfully on a slave even if the data is not 100% in sync, so MySQL doesn't know anything is wrong.  This isn't the case …