MySQL Bugs: #7359: mysqldump: Explanation of --single-transaction

Bug #7359	mysqldump: Explanation of --single-transaction
Submitted:	16 Dec 2004 20:04	Modified:	3 Jan 2005 19:37
Reporter:	Shuichi Tamagawa	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	4.1.8	OS:	Linux (SuSE Linux 9.0)
Assigned to:	Guilhem Bichot	CPU Architecture:	Any

Description:
http://dev.mysql.com/doc/mysql/en/mysqldump.html
In the mysqldump part of the manual, it says

--single-transaction
    This option issues a BEGIN SQL statement before dumping data from the server. It is mostly useful with InnoDB tables and READ COMMITTED transaction isolation level, because in this mode it will dump the consistent state of the database at the time then BEGIN was issued without blocking any applications.

However, READ COMMITTED is not the mode to do consistent read.

How to repeat:
N/A

Suggested fix:
"It is mostly useful with InnoDB tables and READ COMMITED transaction isolation level" 

shoud be

"It is mostly useful with InnoDB tables and REPEATABLE READ transaction isolation level"

I'd also say this should read REPEATABLE READ, not READ COMMITED?

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
product(s).

Additional info:

Heikki has fixed this to say REPEATABLE READ.