… Server for MySQL version 5.1.67-14.4[/caption] Percona is glad to announce the release of Percona Server for MySQL version 5.1.67… log was displayed incorrectly when slow_query_log_microseconds_timestamp variable was set to microseconds. Bug fixed #887928 (Laurynas Biveinis). Upstream bug…
Post: Microslow patch for 5.1.20
July 18, 2007 By 3 Comments
… only for earlier MySQL editions such as 4.1 and 5.0. Now it’s also available for the latest 5.1. Because MySQL went through… time with microsecond resolution. Instead you should redirect the output for your logs to the plain old-fashioned files. In MySQL 5.1 it… or by setting MySQL system variable with SET [SESSION|GLOBAL] long_query_time=n. The value is in microseconds (0 means to…
Post: Percona Server 5.1.47-rel11.0
June 21, 2010 By 13 Comments
… Percona Server is now based on MySQL 5.1.47, and XtraDB is now based on InnoDB plugin 1.0.8. XtraDB now uses… of error code 1592. Added the –microseconds_in_slow_query_log option to use microsecond precision for the slow query log’s… are based on 5.1.x versions Together “Percona-Server-server-51″ is the package name. 5.1.47 is the MySQL version the package…
Post: MariaDB 5.3 is released as GA!
March 5, 2012 By 17 Comments
… fix, and MySQL 5.6 offers microsecond timestamp support, as well as a lot of optimizer improvements. Even the standard MySQL 5.5 offers pluggable authentication…. MariaDB 5.3 isn’t the only exciting thing, however. MariaDB 5.3 is based on MySQL 5.1, but MariaDB 5.5 will be based on MySQL 5.5…
Post: Percona Server 5.5.10 (Release Candidate)
April 4, 2011 By 4 Comments
…_timestamp_always. (Oleg Tsarev) Old system variable slow_query_log_microseconds_timestamp was renamed to slow_query_log_timestamp_precision. (Oleg… on MySQL 5.0 or Percona Server versions prior to 5.1.7 could crash the server. (Yasufumi Kinoshita) MySQL bugs 56433 and 51325 – These MySQL…
Post: Percona Server 5.1.53-12.4
December 29, 2010 By Leave a Comment
Percona Server version 5.1.53-12.4 is now available for download. It is …. Functionality Added or Changed  Percona Server 5.1.53-12.4 is based on MySQL 5.1.53.  New Features Added: Precompiled UDFs…_slow_timestamp_every, log_slow_sp_statements, slow_query_log_microseconds_timestamp, use_global_long_query_time. (Oleg Tsarev) Bug #673567…
Post: How (not) to find unused indexes
October 16, 2009 By 2 Comments
…, but provided that the application is always only sending query 1 to MySQL it’s actually a pretty good index! It…   | NULL | 239 | Using where | +—-+————-+———+——+—————+——+———+——+——+————-+ 1 row in set (0.04 sec) mysql> EXPLAIN SELECT * FROM country WHERE population > 100000000… (like QUAN) or set your slow query log to zero microseconds (5.1 feature) and then find someway to parse and EXPLAIN all…
Post: Guess what?! Microsecond slow query timing finally available in MySQL!
August 29, 2007 By 5 Comments
… 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… out that MySQL incorporated the patch to their release. So it’s a built-in feature now in the 5.1 line. So…
Post: The new cool MySQL patch has landed! Check your queries performance!
October 31, 2007 By 16 Comments
…less than 1s. Now long_query_time is in microseconds and you can set it for example to … # No InnoDB statistics available for this query SELECT COUNT(1) FROM t2; Important note: Although the patch was …on any important system! The patch is available for MySQL Community 5.0.45 on Linux. May not work …
Post: How much overhead DRDB could cause ?
June 2, 2008 By 4 Comments
… not fixed in 5.1 to date. So this is the access pattern which is often going to define your MySQL on DRBD… be 200 microseconds. With such case even considering extra overhead besides network IO we’re speaking about 300 microseconds vs 5000 microseconds and… case you have about 100 microsecond for request execution while DRBD overhead remains at 200-300 microseconds for requests. This means DRBD…
