… 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: 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… of course enable slow logging with –slow-query-log parameter. MySQL 5.1 has this nice feature which allows you to redirect query… time with microsecond resolution. Instead you should redirect the output for your logs to the plain old-fashioned files. In MySQL 5.1 it…
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: 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: Percona Server 5.5.10 (Release Candidate)
April 4, 2011 By 4 Comments
… 5.5.10-20.1 is now available for download. This is a release candidate for the Percona Server 5.5 series. In addition to MySQL 5.5…_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: New patches, new builds
September 5, 2008 By 24 Comments
… it with MySQL 5.1 RC, at least stable to name whole MySQL-5.1-percona release as RC. Along with previously mentioned patches, to 5.1 we added new column TIME_MS to INFORMATION_SCHEMA.PROCESSLIST which contains time of query execution with microseconds granularity. mysql> SELECT…
Post: Heikki Tuuri Innodb answers - Part I
October 26, 2007 By 17 Comments
…: Cool. This is one of little known new features in MySQL 5.1 Q15: How frequently does Innodb fuzzy checkpointing is activated HT… 200) for additional throughput? HT: ha_innodb.cc in 5.1: static MYSQL_SYSVAR_ULONG(thread_concurrency, srv_thread_concurrency, PLUGIN_VAR_RQCMDARG… 5.1 makes no difference. If you have a battery-backed disk controller cache, then the commit returns in less than 100 microseconds…
Post: Percona builds with Percona patchsets
July 16, 2008 By 35 Comments
… customers. Current releases include: microslow patch (enables microsecond resolution in slow logs) execution plan (show …mysql-5.1.26-percona.tar.bz2 md5:0574b38755786a97bc476058051cbe82 You can find the individual patches here: http://www.mysqlperformanceblog.com/mysql-patches/ Besides standard 5.1…
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: How much overhead DRDB could cause ?
June 2, 2008 By 4 Comments
…_flush_log_at_trx_commit=1 and sync_binlog=1 you will have 4 “sync” operations in MySQL 5.0 – there is event written… 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…
