mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 12:02:42 +01:00
BUG#27850 "mysqldump --single-transaction does not work if TRUNCATE/DROP/RENAME/ALTER":
this has already been closed by a note in the manual, now we complete this by a note in "mysqldump --help" client/mysqldump.c: mention, in "mysqldump --help", of limitations reported as BUG#27850 "mysqldump --single-transaction does not work if TRUNCATE/DROP/RENAME/ALTER" The new text is inspired from what the "mysqldump" section of the manual now says about --single-transaction: http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html
This commit is contained in:
parent
8a3e1a5568
commit
f97e4d319d
1 changed files with 6 additions and 2 deletions
|
@ -404,8 +404,12 @@ static struct my_option my_long_options[] =
|
|||
"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. Option "
|
||||
"automatically turns off --lock-tables.",
|
||||
"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.",
|
||||
(gptr*) &opt_single_transaction, (gptr*) &opt_single_transaction, 0,
|
||||
GET_BOOL, NO_ARG, 0, 0, 0, 0, 0, 0},
|
||||
{"skip-opt", OPT_SKIP_OPTIMIZATION,
|
||||
|
|
Loading…
Reference in a new issue