0

Whenever I add --set-gtid-purged=OFF, it still adds @@SESSION.SQL_LOG_BIN=0; to the output.

According to the documentation, shouldn't it get removed?

--set-gtid-purged=OFF: SET @@SESSION.SQL_LOG_BIN=0; is not added to the output.

Dump created by MySQL pump utility, version: 8.0.16, Win64 (x86_64)

SET @@SESSION.SQL_LOG_BIN= 0;

Is this correct behavior for this tool?

  • pump does not know what you will be doing with the resulting data, so I guess it plays it safe by making sure that non-data things are not replicated. – Rick James Jul 2 at 19:19
  • Then whats the point of the cmd switch? By adding this it breaks replication if you were to restore a table to a group replicated environment. – Watson Jul 2 at 19:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.