mysqldump Single-transaction & Set-gtid-purged
(Doc ID 2919859.1)
Last updated on FEBRUARY 20, 2023
Applies to:
MySQL Server - Version 8.0 and laterInformation in this document applies to any platform.
Goal
Is it possible to use mysqldump in a GTID enviroment ?
From the Online Manual, this seems not feasible:
https://dev.mysql.com/doc/refman/en/mysqldump.html#option_mysqldump_single-transaction
Using --single-transaction together with the --set-gtid-purged option is not recommended; doing so can lead to inconsistencies in the output of mysqldump.
Using this option with the --single-transaction option can lead to inconsistencies in the output. If --set-gtid-purged=ON is required, it can be used with --lock-all-tables, but this can prevent parallel queries while mysqldump is being run.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |