[MDEV-33212] mysqldump uses MASTER_LOG_POS with dump-slave Created: 2024-01-10  Updated: 2024-01-10

Status: Open
Project: MariaDB Server
Component/s: Backup
Affects Version/s: 10.11, 11.0, 11.2, 11.3, 11.4
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Wojciech Matusiak Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

mysqldump access 21 index of result array from show slave status as master_log_pos.
Commit 1a057a9 adds column Replicate_Rewrite_DB and move Exec_Master_Log_Pos to 22 position.

This causes dump-slave option to put wrong value in to MASTER_LOG_POS in dump file.

 Comments   
Comment by Kristian Nielsen [ 2024-01-10 ]

Thanks a lot for the informative bug report.

It's not just mysqldump that is the problem, this will break 3rd-party and user scripts as well that rely on the output of SHOW SLAVE STATUS.

The patch 1a057a9 is wrong and needs to be reverted. The output of SHOW SLAVE STATUS must not be changed except to add additional rows at the end, to preserve backwards compatibility.

It's particularly embarrassing to see a change like this go in and break backwards compatibility not just with user's and 3rd-party's scripts, but with a command-line utility mysqldump included with the MariaDB source code itself

Generated at Thu Feb 08 10:37:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.