MySQL Bugs: #26573: Add Option --slave-data to mysqldump

Bug #26573	Add Option --slave-data to mysqldump
Submitted:	22 Feb 2007 16:47	Modified:	13 May 2013 10:24
Reporter:	Sebastian Nohn	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: General	Severity:	S4 (Feature request)
Version:	Irrelevant	OS:	Any (Irrelevant)
Assigned to:		CPU Architecture:	Any
Tags:	mysqldump replication slave

Description:
Currently mysqldump has the option --master-data which puts additional information regarding master log position etc. into a SQL dump to set up a slave based on the dump.

Opposite to this you don't have a chance to get a consistent dump of a slave using mysqldump without stopping slave operation manually before.

How to repeat:
- Dump a slave
- Import that dump some time later into a slave
- You don't have a chance to set that slave to the right master log position

Suggested fix:
Implement a --slave-data option which dumps a database (or server) in a consistent state (e.g. with the required locks) and add the master log position etc. to that dump so that you can import that dump and start the slave and have a consistent state with the master after some time.

Thank you for a reasonable feature request.

Bug #45944  was marked as a duplicate of this one.

This FR was implemented in 5.5.3.

Bug #8368 	mysqldump needs --slave-data option
http://bugs.mysql.com/8368.

Closing this FR as a duplicate.