June 19, 2013

Post: Bug#12704861

MySQL 5.1.60. I’ll repeat here the full documentation from the release notes: “InnoDB Storage Engine: Data from BLOB columns… if the server crashed at a precise moment when other columns were being updated in an InnoDB table. (Bug #12704861)” This… pages that were freed during the B-tree operation by “fake allocating” them prior to writing the BLOBs, and freeing them…

Post: Announcing Percona Server 5.1.66-14.2

… the Percona Software Repositories). Based on MySQL 5.1.66, including all the …. Bug fixed #1012715 (Laurynas Biveinis). Although fake change transactions downgrade the requested exclusive (X…). In cases where indexes with AUTO_INCREMENT columns where correctly detected, mysqldump prevented all …

Post: Percona Server 5.1.59-13.0

…“UPDATE“ and “DELETE“ statements but not updating them (Fake Changes), the rollback is very fast …KEY. #851674 (Alexey Kopytov). Backported fix for MySQL bug #53761 (Wrong estimate for RANGE …InnoDB. #814404 (Yasufumi Kinoshita). Since AUTO_INCREMENT columns must be defined as keys, omitting key…

Post: Percona Server 5.5.16-22.0

… from the Percona Software Repositories). Based on MySQL 5.5.16, including all the bug … “UPDATE“ and “DELETE“ statements but not updating them (Fake Changes), the rollback is very fast as …in InnoDB. #814404 (Yasufumi Kinoshita). Since AUTO_INCREMENT columns must be defined as keys, omitting key …

Post: A recovery trivia or how to recover from a lost ibdata1 file

… the Innodb tablespace id by creating fake Innodb tables Once the Innodb tablespace…lib/mysql/recover/ chown mysql.mysql /var/lib/mysql/recover/$CURRENT_TABLENAME.ibd sleep 1 echo “importing tablespace” mysql…from dev or staging) contained an extra column. With a modified schema, the recovery …