Bug #106973 the statement SET @@GLOBAL.GTID_PURGED= choose a wrong gtid when use mysqldump

• Submitted: 11 Apr 2022 8:50
• Modified: 11 May 2022 13:38
• Reporter: abel longxiao
• Status: No Feedback
• Category: MySQL Server: mysqldump Command-line Client
• Severity: S3 (Non-critical)
• Version: from 5.7.36
• OS: CentOS
• Assigned to: MySQL Verification Team
• CPU Architecture: Any

[11 Apr 2022 8:50] abel longxiao

Description:
the statement SET @@GLOBAL.GTID_PURGED=  choose a wrong gtid when using mysqldump to backup databases;

I found  the statement SET @@GLOBAL.GTID_PURGED= appered in the end of mysqldump backup file. and the GLOBAL.GTID_PURGED choose a wrong gtid sets. so we got errors when using the backup file to add slave or recover database.

the begin version is 5.7.36, 5.7.37 have the same problem

How to repeat:
use mysqldump version at 5.7.36 and 5.7.37

[11 Apr 2022 13:38] MySQL Verification Team

Hi Mr. longxiao,

Thank you for your bug report.

However, we require a full test case, so that we can reliably reproduce it.

Thanks in advance.

[12 May 2022 1:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".