xtrabackup master binlog file and position output is different between versions

Bug #1551721 reported by Hrvoje Matijakovic on 2016-03-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.3
Triaged
Medium
Unassigned
2.4
Triaged
Medium
Unassigned

Bug Description

Originally reported as a comment in the release blog post [1]:

xtrabackup master binlog file and position output is different between versions, output suffix and position in 2.4 is a string and in 2.2 is int.

2.4 output master binlog file and pos:

MySQL binlog position: filename ‘binlog.000006’, position 154
MySQL slave binlog position: master host ‘10.72.1.65’, filename ‘binlog.000007’, position ‘15195’

2.2 or 2.1:

innodbackupex: MySQL binlog position: filename ‘binlog.000006’, position ‘154’
innodbackupex: MySQL slave binlog position: master host ‘10.72.1.65’, filename ‘binlog.000007’, position 15195

[1] https://www.percona.com/blog/2016/02/23/33632/

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-751

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers