Comment 5 for bug 1180905

Hi James,

Thanks so much! That was the quickest bug fix I have ever seen.

Cheers!
Marc

On May 17, 2013, at 7:04 AM, James Dooley <email address hidden> wrote:

> Did a quick test of the specific portion of the patch related to this
> bug, everything seems to be working properly now.
>
> --
> You received this bug notification because you are subscribed to Percona
> XtraBackup.
> Matching subscriptions: xtrabackup21
> https://bugs.launchpad.net/bugs/1180905
>
> Title:
> percona-xtrabackup 2.1 + 5.1 w/ innodb plugin
>
> Status in Percona XtraBackup:
> Fix Committed
> Status in Percona XtraBackup 2.1 series:
> Fix Committed
>
> Bug description:
> As I understand percona-xtrabackup 2.1 still supports MySQL 5.1 as
> long as the innodb-plugin is being used. However, attempting to do so
> fails:
>
> # mysql -se 'SELECT @@version, @@innodb_version'
> @@version @@innodb_version
> 5.1.67-log 1.0.17
>
> # mysql -e 'SHOW PLUGINS' | grep InnoDB
> InnoDB ACTIVE STORAGE ENGINE ha_innodb_plugin.so GPL
>
> # innobackupex $HOME/backup
> innobackupex: Error: Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0. at /usr/bin/innobackupex line 387.
>
> This is due to the check here:
>
> if($var_version =~ m/5\.1\.\d/ && $var_innodb_version =~ m/.*/) {
> Die "Support for MySQL 5.1 with builtin InnoDB (not the plugin) was removed in Percona XtraBackup 2.1. The last version to support MySQL 5.1 with builtin InnoDB was Percona XtraBackup 2.0.";
> }
>
> I suppose this check intends to look for an empty/missing
> innodb_version instead.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1180905/+subscriptions