holland-coredev team mailing list archive
-
holland-coredev team
-
Mailing list archive
-
Message #00119
[Bug 766676] Re: Require lockless backup
** Changed in: holland-backup
Milestone: None => 1.1.0a2
** Changed in: holland-backup
Importance: Undecided => Low
** Changed in: holland-backup
Status: New => In Progress
** Changed in: holland-backup
Assignee: (unassigned) => Andrew Garner (muzazzi)
--
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:
In Progress
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.
References