Merged into amsterdam branch here:
https://github.com/holland-
backup/holland/tree/98feea3930159bdee5fa2ddbae7dc79f1530212b
** Changed in: holland-backup
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/766676
Title:
Require lockless backup
Status in Holland Backup Framework:
Fix Committed
Bug description:
It would be nice to have an option where you require that the backup
fail if it can not be completed without locking. There are cases where
I would rather have no backup for the night than downtime.
An example would be a database which is pure innodb having a new table
accidentally created as MyISAM. Ordinarily this would just downgrade
from --single-transaction to --lock-tables but it would be nice to
have an option where instead the backup refuses to start until the
table is converted to a transactional engine.
_______________________________________________
Mailing list: https://launchpad.net/~holland-coredev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~holland-coredev
More help : https://help.launchpad.net/ListHelp
