Bug #67674 flush-logs with single-transaction doesn't flush logs at each table dumping
Submitted: 22 Nov 2012 1:54 Modified: 1 Feb 2013 13:38
Reporter: tsubasa tanaka (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5.21 and later, 5.6.8 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any
Tags: doc, mysqldump

[22 Nov 2012 1:54] tsubasa tanaka
Description:
flush-logs option is described that

"If you use this option in combination with the --all-databases option, the logs are flushed for each database dumped. The exception is when using --lock-all-tables or --master-data"

at Document of 5.5 and 5.6.

But flush-logs with single-transaction doesn't flush at each table dumping any longer, after modify at 5.5.21.

How to repeat:
mysqldump --all-databases --flush-logs --single-transaction

Suggested fix:
Modify documents.

"If you use this option in combination with the --all-databases option, the logs are flushed for each database dumped. The exception is when using --lock-all-tables or --master-data or --single-transaction(only 5.5.21 and later)"
[22 Nov 2012 11:17] MySQL Verification Team
Thank you for the bug report.
[1 Feb 2013 13:38] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.