June 20, 2013

Post: Percona XtraBackup 2.0.7 for MySQL available for download

Dump/Restore of the Buffer Pool in Percona Server. MySQL 5.6 buffer pool dumptables. Bug fixed #1169169. Tables that were dropped between taking a full backup and an incremental one were present in the full

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

… on May 7, 2013. Downloads are available from our download site here. For this RC … to the Dump/Restore of the Buffer Pool in Percona Server. MySQL 5.6 buffer pool dump is …tables. Bug fixed #1169169. Tables that were dropped between taking a full backup and an incremental one were present in the full

Post: How to create/restore a slave using GTID replication in MySQL 5.6

… because there are many documents about that: http://dev.mysql.com/doc/refman/5.6/en/replication-gtids-concepts….table-sync. How to restore a slave in a good and slow way The good way is mysqldump again. We take a dump from… a one when we publish a xtrabackup version with full support of GTID.

Post: Improved InnoDB fast index creation

… > dump_optimized.sql $ time mysql -uroot test < dump_unoptimized.sql real 2m52.785s user 0m3.179s sys 0m0.069s $ time mysql -uroot test < dump_optimized… requires a full table rebuild on foreign key changes. So adding them back with a separate ALTER TABLE after restoring the data from a dump would…

Post: Percona Server 5.5.16-22.0

…are available here and from the Percona Software Repositories). Based on MySQL 5.5.16…restore (in 5.1 it is –innodb-blocking-lru-restore), which is OFF by default. When set to ON, restoring from the LRU dump…(Alexey Kopytov). Bugs Fixed InnoDB requires a full table rebuild for foreign key changes. …

Post: Percona Server 5.1.59-13.0

…Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.59, …blocking-lru-restore, which is OFF by default. When set to ON, restoring from the LRU dump file is …858945 (Alexey Kopytov). Bugs Fixed InnoDB requires a full table rebuild for foreign key changes. This …

Post: Innodb Recovery Update - The tricks what failed.

dumping in reimporting couple of tables rather than full dump and restore. The bug which we found during attempt to dump tables… things: Versions later than MySQL 5.0.33 are …dump and restore from backup. I think this is the main reason. In fact dump and reload process can be so slow restoring

Post: Announcing Percona Server 5.1.65-14.0

…are available here and from the Percona Software Repositories). Based on MySQL 5.1.65…full data scans. New table INNODB_CHANGED_PAGES has been implemented. This table contains a list of modified pages fromdump. Bug fixed #713481 (George Ormond Lorch III). Fixed issue where innodb_blocking_lru_restore

Post: Percona Server 5.1.58-12.9

… for those upgrading from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL bug (#27877… widely used. Instead, we recommend using the much safer LRU Dump/Restore patch, which provides similar improvements in restart performance and has… dump/restore here. Bug Fixes When adding a table to the cache, the server may evict and close another if the table cache is full

Post: Percona Server and XtraBackup weekly news, April 4th

… of developments in the market such as MySQL 5.5, MariaDB, Drizzle, etc. The short …. (Full details). Alexey made Percona Server use “fast index creation” for ALTER TABLE and OPTIMIZE TABLE, which …xtrabackup copy the LRU dump file from Percona Server, so that after the backup is restored, the server …