Re: "mysqldump --single-transaction" and "--lock-tables"

[Dimitry Butko]

(non-authoritative answer)

Yes, as far as I can see from the documentation

......

This option issues a BEGIN SQL statement before dumping data from
the server. It is useful only with transactional tables such as
InnoDB and BDB, because then it dumps the consistent state of the
database at the time when BEGIN was issued without blocking any applications.

When using this option, you should keep in mind that only InnoDB
tables are dumped in a consistent state. For example, any MyISAM or
MEMORY tables dumped while using this option may still change state.

The --single-transaction option and the --lock-tables option are
mutually exclusive, because LOCK TABLES causes any pending
transactions to be committed implicitly.

This option is not supported for MySQL Cluster tables; the results
cannot be guaranteed to be consistent due to the fact that the
NDBCluster storage engine supports only the READ_COMMITTED
transaction isolation level. You should always use NDB backup and
restore instead.

To dump big tables, you should combine this option with --quick