… of Percona Monitoring Plugins 1.0.3 for MySQL — high-quality components to add enterprise-grade MySQL monitoring and graphing capabilities…MySQL 5.6 compatibility for InnoDB graphs (bug 1124292) * Added performance data to Nagios plugins (bugs 1090145, 1102687) * Added UTC option to pmp-check-mysql…
Post: Announcing Percona XtraBackup 2.1.1 GA
May 15, 2013 By Leave a Comment
…DBD::MySQL package for server communication instead of spawning the MySQL command line client. Support for InnoDB 5.0 and InnoDB 5…. directory. Bug fixed #1174314. Other bugs fixed: bug fixed #1166713, bug fixed #1175581, bug fixed #1175318, bug fixed #1175309, bug fixed #1176198, bug fixed #1175566…
Post: Understanding the maximum number of columns in a MySQL table
April 8, 2013 By 5 Comments
… reports. This evolved into the SQL based MySQL, with MySQL 1.0 being released in 1995. The FoRM file … is this: /* Hack to avoid bugs with small static rows in MySQL */ reclength=max(file->min_record_length(…_TO_BIG_ROW); } Which is curiously gone from MySQL 5.6, it’s replaced by the following set …
Comment: Percona XtraBackup 2.0.7 for MySQL available for download
May 14, 2013 By 1 Comment
I came to the bug https://bugs.launchpad.net/percona-xtrabackup/+bug/945161 while using percona-xtrabackup-2.0.6, so I update this…_buffer_pool_filename’ option in group ‘mysqld’ in MySQL options” My server is MySQL 5.5, my command is “innobackupex –defaults-file=/etc/my3…” innodb_buffer_pool_filename is not a global variable of MySQL 5.5, why this error? thanks!
Comment: MySQL and Percona Server in LinkBench benchmark
May 11, 2013 By 18 Comments
… LinkBench with 5.6 a little. Though I have not identified the actual bug# yet, the problem…around 6000 — mysql-5.6-dev (doublewrite) 64 around 16000 16 around 12000 4 around 5500 mysql-5.6-dev …innodb_io_capacity_max = 100000 innodb_read_ahead_threshold = 0 innodb_change_buffer_max_size = 1 innodb_…
Post: Implications of Metadata Locking Changes in MySQL 5.5
February 1, 2013 By 9 Comments
… large number of MySQL 5.0 and 5.1 installations that would upgrade or are in the process of upgrading to MySQL 5.5, I thought it… Meta Data Locking behavior prior to MySQL 5.5.3 Metadata Locking behavior prior to MySQL 5.5.3 Prior to MySQL 5.5.3 a statement that opened… really documented and as such I have reported a bug: http://bugs.mysql.com/bug.php?id=67647 Metadata locking behaves differently for queries…
Post: 5.0.86-build19 Percona binaries
October 12, 2009 By 10 Comments
… on MySQL-5.0.86 Fix from Neil Katin to userstatv2.patch fix InnoDB slowness with large queries Fixed bugs in the build: Bug #413858… http://www.percona.com/mysql/5.0.86-b19/ There is Debian packages repository available since Build 19. To install MySQL with Percona patches… install mysql-server-5.0 The Percona patches live on Launchpad : https://launchpad.net/percona-patches and you can report bug to Launchpad bug system…
Post: Binaries of MySQL 5.0.33 Community release for AMD64 / EM64T
January 12, 2007 By 37 Comments
… more than a year ago. Great news are MySQL finally released new Community release – MySQL 5.0.33, which however as promised comes without… to use MySQL Community version but does not like to build binaries we decided to publish our build for MySQL 5.0.33 Community….com/2006/09/06/slow-query-log-analyzes-tools/ http://bugs.mysql.com/bug.php?id=25412 Also we propose Linux (AMD64 / Intel…
Post: 5.0.87-build20 Percona binaries
November 18, 2009 By 3 Comments
… build is based on MySQL-5.0.87 innodb_rw_lock.patch is ported from InnoDB Plugin 1.0.3 To be compatible with…/$basearch/ gpgcheck=0 As usual you can download binaries and sources with the patches here http://www.percona.com/mysql/5.0.87-b20… : https://launchpad.net/percona-patches and you can report bug to Launchpad bug system: https://launchpad.net/percona-patches/+filebug. The documentation…
Post: MySQL 5.0 Community Edition Regression
July 27, 2007 By 2 Comments
… in latest MySQL Community Edition and I’ve been troubleshooting customer affected by one of these very issues today. The Bug can dramatically increase System CPU usage (about 10 times in this case) The “fix” was to get MySQL 5.0.44 sources…
