Sveta Smirnova
Sveta Smirnova
Just sent pull request for this: https://github.com/juanmirocks/Levenshtein-MySQL-UDF/pull/19
You can have the same behavior if you use the option --fail-successive-errors.
Closing because this PR duplicates fix for PT-2029 that additionally re-structures the guide.
Thank you for your contribution. According to the comment: > \# Even if the db already exists, do this in case it does not exist > \# on a slave....
OK, that makes sense regarding 8.1 Awaiting tests.
This is not a bug but documented behavior. Check https://docs.percona.com/percona-toolkit/pt-archiver.html#cmdoption-pt-archiver--[no]safe-auto-increment and https://jira.percona.com/browse/PT-1349 for details.
We may need to check if other tools require similar fix.
Currently, you can provide a replica username and password as part of the DSN.
Recursion method DSNS is available for pt-table-checksum and pt-table-sync: https://docs.percona.com/percona-toolkit/pt-table-checksum.html#cmdoption-pt-table-checksum-recursion-method, and this is, definitely, better method. So closing this PR.
Actually looks like this issue is already fixed in the 3.x branch by using operator || and variable innodb_version: ``` section "InnoDB" local have_innodb="$(get_var "have_innodb" "$dir/mysql-variables")" local innodb_version="$(get_var "innodb_version" "$dir/mysql-variables")"...