June 19, 2013

Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download

writing). New Features: This version of Percona XtraBackup has implemented full support for new MySQL 5to different implementation in MySQL 5.6 error messages were not printed to stderr directly. Because of that all InnoDB error

Post: How Percona does a MySQL Performance Audit

… Linux Server release 5.2 (Tikanga) …–log-error=/var/log/mysqld.log mysql 3172 3137 78 Nov19 ? 1fails, then you know from the errorto use a patched binary, we can use MySQL Proxy, packet sniffing, or other techniques to get more information than the slow log… need to really know how to write queries…

Post: SHOW INNODB STATUS walk through

MySQL 5failed foreign key constraint: ———————— LATEST FOREIGN KEY ERRORLOGLog sequence number 84 3000620880 Log flushed up to 84 3000611265 Last checkpoint at 84 2939889199 0 pending log writes, 0 pending chkp writes 14073669 log

Post: Announcing Percona Server for MySQL version 5.1.67-14.4

MySQL version 5.1.67-14.4 on March 8, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1to innodb_max_changed_pages. Bug fixed #1105726 (Laurynas Biveinis). Writing bitmap larger than 4GB would cause write to fail. Also a write error

Post: Updated msl (microslow) patch, installation walk-through!

mysql-5.0.51a) % su root Password: First you should apply the changes to the database configuration, specifically you need to enable slow logginglogged while doing it only for every n-th of them thus limiting the number of writes to the log. Note: this feature will fail to

Post: Percona Server 5.1.47-rel11.0

log_warning_1592 option to disable logging of error code 1592. Added the –microseconds_in_slow_query_log option to use microsecond precision for the slow query logfails to compile with CFLAGS=-DUNIV_DEBUG #569156 CentOS 5: mysql-server conflicts with MySQL

Post: MySQL Crash Recovery

…system extremely slow and …to use innodb-safe-binlog option in MySQL 4.1 so your Innodb log and binary log are synchronized. In MySQL 5MySQL to fail with wierd error messages. In MySQL 4.1to MySQL Crash Recovery – Restoring data from backup, corrupted Innodb tablespace recovery etc but I should write