Bug #1632 mysqldump --single-transaction problem in READ-COMMITTED
Submitted: 23 Oct 2003 1:29 Modified: 10 Jun 2005 12:59
Reporter: Peter Zaitsev (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:all OS:Any (all)
Assigned to: Magnus Blåudd CPU Architecture:Any

[23 Oct 2003 1:29] Peter Zaitsev
Description:
mysqldump --single-transaction  designed to create consistent backup
of Innodb tables does not work if isolation mode is set to one lower than REPEATABLE-READ

How to repeat:
Set mode to READ-commited,
start consistent backup and during it do few modifications to the tables which were backed up and were not yet, you'll see only part of your changes.

Suggested fix:
Make --single-transaction to set isolation level to repeatable-read for its session
[10 Jun 2005 12:59] Magnus Blåudd
This bug was fixed when Guilhem fixed "#7850: mysqldump --single-transaction should force transaction isolation level"