'flush logs local' after flushing tables

Bug #1498184 reported by Andreas Piesk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mylvmbackup
Confirmed
Medium
Lenz Grimmer

Bug Description

it's not a bug, more an possible improvement.

I'm not sure, why mylvmbackup does not flush logs locally after flushing the tables. it's technically not necessary but i prefer to have a log with all the changes consistent to the full backup.
the patch does not change the default behaviour, flushing logs must be explicitely enabled. the flushing i didn't patch the documentation because i don't know exactly how without breaking something.

another question: why not use "local" for table flushing too? i don't think the flush statement should be written to the binlog.

Revision history for this message
Andreas Piesk (a-piesk) wrote :
Revision history for this message
Lenz Grimmer (lenzgr) wrote :

Sounds reasonable, thank you! Another one for the 0.17 release, I think.

Changed in mylvmbackup:
assignee: nobody → Lenz Grimmer (lenzgr)
importance: Undecided → Medium
milestone: none → 0.17
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers