EmergencyEMERGENCY? Get 24/7 Help Now!

Guess what?! Microsecond slow query timing finally available in MySQL!


Posted on:

|

By:


PREVIOUS POST
NEXT POST
Share Button

Vadim asked me yesterday to update Microslow patch for 5.1.21, because the previous one I wrote for 5.1.20 failed to apply correctly on the new MySQL release. Imagine the expression on my face after I unpacked the sources and found out that MySQL incorporated the patch to their release. So it’s a built-in feature now in the 5.1 line. So far I noticed one addition to my code which is logging the microtime statistics into TABLE type log storage.

Maciek

Share Button
PREVIOUS POST
NEXT POST


Maciej Dobrzanski

Maciek is a former Percona employee. An IT consultant with the primary focus on systems, databases and application stacks performance and scalability. Expert on open source technologies such as Linux, BSD, Apache, nginx, MySQL, and many more. Co-author of dba square - a blog about how to manage, scale, and optimize MySQL performance!



Tags:

,

Categories:
Insight for DBAs


Comments
  • Maciek,

    How was it done for table format – previously there was TIME column for query execution time which did not support fractions of seconds in MySQL – was data type extended or the column changed to different type ?

    Also was only pure timing support added to the MySQL 5.1.20 or were other features you’ve implemented, such as logging slow queries from replication thread as well and having rows examined and rows updated in the slow query log added as well.

    In any case it is great news Monty finally pulled the trigger on this one as it was long overdue. He also told me he planned to see if more efficient platform specific timing could be used on some platforms – did you see if there are any changes in this respect ?

    Reply

  • Alexander Mikhailian

    Gongratulations from the developers tired to recompile their MySQL everytime they needed a new version, just to include you (in)famous patch.

    Reply

  • Congratulations, Maciek! Now we need to wait for final 5.1 release and then we’ll be able to use it w/o all these boring patching procedures. Looks like 5.1 is going to give us really great set of new features which will make mysql even better.

    Reply

  • And on a more general note, why on Earth were you not notified by our development team that your patch had been included in 5.1? This is troubling for us in the community team, as we want our contributors to feel the love from MySQL and not be ignored. I’ll check into this…

    Thanks, Maciek, for your patch!

    -jay

    Reply

  • Jay,

    We new it is in the queue for 5.1 but were surprised it was included that quickly.
    I guess as MySQL 5.1 is getting close to “GA” release it just become “now or never” question :)

    Reply

Leave a Reply

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.

Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.

No, thank you. Please do not ask me again.