holland-coredev team mailing list archive
-
holland-coredev team
-
Mailing list archive
-
Message #00156
[Bug 766688] Re: Same backupset per database lock-method
This is similar to https://bugs.launchpad.net/holland-backup/+bug/670192
This fix for that bug should address this case and was merged into
holland-backup/holland here:
https://github.com/holland-
backup/holland/tree/d9cc5e601e901dbfed0b9530ab2f384e1c33b025
** Changed in: holland-backup
Status: New => Fix Committed
** Changed in: holland-backup
Assignee: (unassigned) => Andrew Garner (muzazzi)
** Changed in: holland-backup
Milestone: None => 1.1.0a2
** Changed in: holland-backup
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/766688
Title:
Same backupset per database lock-method
Status in Holland Backup Framework:
Fix Committed
Bug description:
Currently if you want to force --single-transaction for a particular
database, you have to have it in a separate backupset. If you want to
use file-per-database, it might be nice to be able to modify lock-
method on a per database level without creating a new backupset.
References