Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
5.5.32, 5.5(EOL)
Description
from
/usr/bin/mysqldump -u backup --all-databases --extended-insert --dump-slave=2 --master-data=2 --include-master-host-port --single-transaction --no-data
|
only the following replication position was recorded.
-- CHANGE MASTER TO MASTER_HOST='127.0.0.1', MASTER_PORT=4041, MASTER_LOG_FILE='mariadb-bin.000047', MASTER_LOG_POS=31738774;
|
Its useful too have both since in a backup scenario its unknown whether the dump is going to be use used to replace the master or configured as the new slave.
Attachments
Issue Links
- is part of
-
MDEV-4551 mysqldump --dump-slave fails with multi-source replication
- Closed
- relates to
-
MDEV-32611 Test suite is missing dump option delete-master-logs
- Closed
- links to