Consistent dumps of non-transactional tables
Registered by
Domas Mituzas
Dump would have to be done with multiple passes - first one would dump non-transactional tables, unlock would be done, second pass would dump transactional tables.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Andrew Hutchings
- Definition:
- New
- Series goal:
- Accepted for 0.2
- Implementation:
-
Implemented
- Milestone target:
-
0.2.2
- Started by
- Andrew Hutchings
- Completed by
- Andrew Hutchings
Whiteboard
my branch is a little bit more advanced than 2-pass:
1. flush with read lock
2. Dump non-InnoDB
3a. Start InnoDB dump
3b. When non-InnoDB dump has finished (whilst InnoDB is dumping) unlock tables
4. ...
5. Profit
(?)
