This bug (#837143) is said to be a re-incarnation of this:
https://bugs.launchpad.net/percona-xtrabackup/+bug/402884
Bug #402884 says it is due to the following MySQL/InnoDB bugs:
http://bugs.mysql.com/bug.php?id=41609 http://bugs.mysql.com/bug.php?id=45638 http://bugs.mysql.com/bug.php?id=45976
The first 2 of those had been fixed, but not the last, 45976.
However, bug 45976 was recently fixed in MySQL 5.1.62, 5.5.22, and 5.6.5.
Is it reasonable to expect that this bug (#837143) can now be fixed?
Or, is the latest 2.0 Xtrabackup built off a newer version where this would not occur?
Or, would the an even older Xtrabackup work fine as long as the user is using a MySQL that contains this fix?
This bug (#837143) is said to be a re-incarnation of this:
https:/ /bugs.launchpad .net/percona- xtrabackup/ +bug/402884
Bug #402884 says it is due to the following MySQL/InnoDB bugs:
http:// bugs.mysql. com/bug. php?id= 41609 bugs.mysql. com/bug. php?id= 45638 bugs.mysql. com/bug. php?id= 45976
http://
http://
The first 2 of those had been fixed, but not the last, 45976.
However, bug 45976 was recently fixed in MySQL 5.1.62, 5.5.22, and 5.6.5.
Is it reasonable to expect that this bug (#837143) can now be fixed?
Or, is the latest 2.0 Xtrabackup built off a newer version where this would not occur?
Or, would the an even older Xtrabackup work fine as long as the user is using a MySQL that contains this fix?