Difference between revisions of "Mysqldump --single-transaction"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 6: | Line 6: | ||
single transaction. Works ONLY for tables stored in | single transaction. Works ONLY for tables stored in | ||
storage engines which support multiversioning (currently | storage engines which support multiversioning (currently | ||
− | only InnoDB does); the dump is NOT guaranteed to be | + | only [[InnoDB]] does); the dump is NOT guaranteed to be |
consistent for other storage engines. While a | consistent for other storage engines. While a | ||
--single-transaction dump is in process, to ensure a | --single-transaction dump is in process, to ensure a | ||
Line 16: | Line 16: | ||
+ | [[mysqldump --help]] | ||
+ | [[mysqldump --skip-lock-tables]] | ||
+ | [[nice]] | ||
− | {{mysqldump}} | + | == See also == |
+ | * {{mysqldump}} | ||
+ | * {{InnoDB}} | ||
+ | |||
+ | [[Category:MySQL]] |
Latest revision as of 06:34, 9 June 2024
--single-transaction Creates a consistent snapshot by dumping all tables in a single transaction. Works ONLY for tables stored in storage engines which support multiversioning (currently only InnoDB does); the dump is NOT guaranteed to be consistent for other storage engines. While a --single-transaction dump is in process, to ensure a valid dump file (correct table contents and binary log position), no other connection should use the following statements: ALTER TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE, as consistent snapshot is not isolated from them. Option automatically turns off --lock-tables.
mysqldump --help mysqldump --skip-lock-tables nice
See also[edit]
Advertising: