Consistent partial table dumps with mysqldump

Bug #1610670 reported by Ryan Brothers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

I am running Percona Server 5.6 and using mysqldump to do partial table dumps for a large number of tables. I'm doing this by calling mysqldump once for each table, passing in a different --where clause for each table.

This method works great except that the dump as a whole isn't consistent because mysqldump created a separate transaction each time it was called.

I see that Percona Server supports the following statement where it pulls the snapshot details from another session:

START TRANSACTION WITH CONSISTENT SNAPSHOT FROM SESSION <session_id>;

Would it be possible to allow the session_id to be passed to mysqldump, perhaps as an argument to --single-transaction, and have it use that session rather than create a new snapshot?

Thanks for your help.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3509

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.