MySQL Bugs: #23344: mysqldump lacks ability to dump MyISAM and InnoDB tables concurrently

Bug #23344	mysqldump lacks ability to dump MyISAM and InnoDB tables concurrently
Submitted:	16 Oct 2006 20:13	Modified:	5 Aug 2010 13:02
Reporter:	Mark Leith	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: mysqldump Command-line Client	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	innodb, myisam, mysqldump

Description:
mysqldump can currently only use FLUSH TABLES WITH READ LOCK, and lock *all* tables, for a consistent backup when using both MyISAM and InnoDB.

This feature request is to add the functionality to mysqldump so that both MyISAM and InnoDB tables can be dumped by two seperate "threads", one of which locks all MyISAM tables at the start of the backup, and concurrently a second thread acts as if using --single-transaction, for InnoDB.

How to repeat:
No test case

Suggested fix:
o Thread 1 issue LOCK TABLES <MyISAM tables>
o Thread 2 issue LOCK TABLES <InnoDB tables>
o Thread 2 grab --master-data
o Thread 2 fork --single-transaction for InnoDB
o Thread 2 UNLOCK TABLES <InnoDB tables>
o Thread 1 dump all MyISAM tables
o Thread 1 UNLOCK TABLES <MyISAM tables>
o Thread 2 dump all InnoDB tables
o Thread 2 COMMIT;

Hi,
is the implementation of this feature request planned?
thanks
Sebastian

I'd say this is a duplicate of bug #12999. As for implementation, take a look at https://launchpad.net/mydumper