MySQL Bugs: #65553: mysqldump --single-transaction warning is invalid since MySQL 5.5.3

Bug #65553	mysqldump --single-transaction warning is invalid since MySQL 5.5.3
Submitted:	7 Jun 2012 12:52	Modified:	11 Mar 2013 19:30
Reporter:	Tomas Creemers	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.5	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any
Tags:	mysqldump

Description:
The mysqldump documentation states:
"While a --single-transaction dump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection can use the following statements: ALTER TABLE, CREATE TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE. Because a consistent read is not isolated from those statements, using them on a table being dumped can cause the underlying SELECT statement of mysqldump to return incorrect contents or fail."

However, according to the whitepaper "MySQL 5.5: Storage Engine Performance Benchmark for MyISAM and InnoDB" and according to "8.10.4. Metadata Locking Within Transactions", this is no longer the case since MySQL 5.5.3:
"As of MySQL 5.5.3, the server achieves this by acquiring metadata locks on tables used within a transaction and deferring release of those locks until the transaction ends."

How to repeat:
Read https://dev.mysql.com/doc/refman/5.5/en/metadata-locking.html .
Read https://dev.mysql.com/doc/refman/5.5/en/mysqldump.html#option_mysqldump_single-transaction .

Suggested fix:
Add a note to the mysqldump documentation section quoted in this bug description (https://dev.mysql.com/doc/refman/5.5/en/mysqldump.html#option_mysqldump_single-transaction) indicating that the extra caution is no longer required since MySQL 5.5.3.

Thank you for the documentation request.

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.