Details
-
Type:
Task
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Fix Version/s: 10.2
-
Component/s: None
-
Labels:None
Description
Have a Lock for DDL's.
So i.e.ALTER TABLE, DROP TABLE would not break (single-transaction) Dumps.
You can use flush tables with read lock, but then you need not to do a
single-transaction dump anyway.
Even xtrabackup got troubles:
https://bugs.launchpad.net/percona-xtrabackup/+bug/722638
I got to confess I think ignoring tablespace ids is the right solution.
Gliffy Diagrams
Attachments
Issue Links
- duplicates
-
MDEV-8436 Implement "Backup Locks" such as "LOCK TABLES FOR BACKUP" and "LOCK BINLOG FOR BACKUP"
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
In the end we need something like LOCK TABLES FOR BACKUP like with Percona:
http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html