The MySQL Release Notes should be part of any DBA’s regular reading list. The Changes in MySQL 5.6.20 came out last week and there are some interesting goodies.

• MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel.
• A new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error.
• The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL

5.6.20 has a slew of bug fixes, functionality changes, and notes.

So why should you be reading the changes on a regular basis? There isa goldmine of information in them. For instance, if you use blobs, consider this: …

Percona Replication Manager (PRM) continues to evolve and improve, I want to introduce two new features: Slave resync and Async stop.

Slave resync

This behavior is for regular non-gtid replication.  When a master crashes and is no longer available, how do we make sure all the slaves are in a consistent state. It is easy to find the most up to date slave and promote it to be the new master based on the master execution position, the PRM agent already does that but how do we apply the missing transactions to the other slaves.

In order to solve that problem, I modified a tool originally written by Yelp, that outputs the MD5 sums of the payload (XID boundaries) and the commit positions of a binlog file. It produces an output like:

root@yves-desktop:/home/yves/src/PRM/percona-pacemaker-agents/tools/prm_binlog_parser# ./prm_binlog_parser.static.x86_64 /opt/prm/binlog.000382 | tail -n 5 …

Europe traditionally doesn’t have many MySQL-dedicated conferences, which is why I personally enjoy Percona Live London, now in its 2014 Edition. This year it happens November 3-4, and the call for presentations is still open — till August 17th.

The topic list is growing as the MySQL ecosystem matures: DevOps, cloud, security, case studies and what’s new are things you don’t often see. Tutorials are also welcome, of course.

Location-wise, London can’t be beat. And happening at Gloucester Road, you’re on the District/Circle/Picadilly lines to go to many fun places.

If you don’t want to present, do attend – …

#DBHangOps 08/07/14 -- Spatial Indexes, GTID, and more!

If you missed the hangout, check out the recording below:

Hello everybody!

Join us at #DBHangOps this Thursday, August, 07, 2014 at 11:00am pacific (18:00 GMT), to participate in the discussion about:

• Spatial Indexes with Matt Lord

  • What they are
  • How they work
  • When to use them
• GTIDs in MariaDB
• Upcoming InnoDB Data Dictionary changes

Be sure to check out the #DBHangOps twitter search, the @DBHangOps twitter feed, or this blog post to get a link for the google hangout on Thursday!

See all of you on Thursday!

Show notes

We are pleased to inform you that the new Continuent Tungsten 2.0.3 is now available. This is a recommended release for all Continuent Tungsten clustering customers as it contains important updates and improvements to the stability of the manager component, specifically with respect to possible stalls and memory usage that would cause manager failures:

A number of fixes to the Manager

Martin Arrieta and I gave an online presentation last week on “Putting MySQL Fabric To Use.” If you missed it, you can find a recording and the slides here, and the vagrant environment we used plus a transcript of the commands we ran here (be sure to check out the ‘sharding’ branch, as that’s what we used during the webinar).

Thank you all for attending and asking interesting questions. We were unable to answer all of them in the scheduled time, so here are our replies to all the questions.

What is GTID? And how does it relate to MySQL Fabric?
GTID stands for Global …

The binary and source versions of MySQL Utilities/MySQL Fabric have now been made available at http://dev.mysql.com/downloads/utilities/.

This release contains bug fixes and minor enhancements – full details can be found in the MySQL Fabric/MySQL Utilities release notes.

I will be presenting two webinars in August:

• Aug 6, 10 a.m. PDT: Advanced Query Tuning in MySQL 5.6 and Beyond
• Aug 13, 10 a.m. PDT:  Using Performance Schema to Monitor and Troubleshoot MySQL 5.6

This Wednesday’s webinar on advanced MySQL query tuning will be focused on tuning the “usual suspects”: queries with “Group By”, “Order By” and subqueries; those query types are usually perform bad in MySQL and add an additional load as MySQL may need to create a temporary table(s) or perform a filesort. New this year: I will talk more about new MySQL …

Mon, 2014-08-04 13:00benstillman

Today we're going to cover how to upgrade MySQL 5.1 to MariaDB 10 on Centos 6 in place. This tutorial is a general outline, and the steps were performed on an out-of-the-box install of MySQL 5.1. Do be careful to check your configuration file(s) when completed.

Information on variables and other changes:
http://dev.mysql.com/doc/refman/5.5/en/upgrading-from-previous-series.html
http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
…

HandlerSocket is included with MariaDB and acts like a simple NoSQL interface to InnoDB, XtraDB and Spider and I will describe it a bit more in this and a few upcoming blogs.

So, what is HandlerSocket? Adam Donnison wrote a great blog on how to get started with it, but if you are developing MariaDB applications using C, C++, PHP or Java what good does HandlerSocket do you?

HandlerSocket in itself is a MariaDB plugin, of a type that is not that common as is is a daemon plugin. Adam shows in his blog how to enable it and install it, so I will not cover that here. Instead I will describe what it does, and doesn't do.

A daemon plugin is a process that runs "inside" the MariaDB. A daemon plugin can implement anything really, as long as it is …