Comment 0 for bug 1455191

Getting a snapshot from a database in a Percona server (configured for Fabric) results in a "bingo_pos = GTID of the last change" that breaks up into multiple lines when there are multiple GTID ranges specified.

Specifically, running a snapshot using the following command:

    innobackupex --host=127.0.0.1 --user=root --password=$p --rsync --safe-slave-backup --slave-info /var/backups/mysql/daily_snapshot 2>&1 | egrep "innobackupex|xtrabackup" | tee -a /var/log/daily_snapshot_$sdate.log
    sdir=$(ls -1 | egrep "^$sdate")
    innobackupex --host=127.0.0.1 --user=root --password=$p --apply-log /var/backups/mysql/daily_snapshot/$( ls -1 /var/backups/mysql/daily_snapshot/ | grep $sdir) 2>&1 | egrep "innobackupex|xtrabackup" | tee -a /var/log/daily_snapshot_$sdate.log

the resulting xtrabackup_info file contains these 2 lines:

    binlog_pos = GTID of the last change 'f43a8a6b-c136-11e4-b41c-f23c9133c356:1-219456761,
    f465b62d-f288-11e4-b5b8-f23c91189be4:1-39'

-note that the white-space after the comma has been reinterpreted as a carriage return, only in xtrabackup_info.

In xtrabackup_slave_info the resulting quoted value makes more sense:

    SET GLOBAL gtid_purged='f43a8a6b-c136-11e4-b41c-f23c9133c356:1-219456761, f465b62d-f288-11e4-b5b8-f23c91189be4:1-39';

-versions:

Percona Server Release 72.1 Revision 0503478

xtrabackup version 2.2.10 based on MySQL server 5.6.22 Linux (x86_64) (revision id: )

innobackupex version: InnoDB Backup Utility v1.5.1-xtrabackup