This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
the default value of
max_allowed_packet
in MySQL server and go-sql-driver/mysql driver is 4MB, but in TiDB server it's 64MB.ref:
What is changed and how it works?
max_allowed_packet
to 64MBmax-allowed-packet
config item for DB configcharset
fromutf8
toutf8mb4
we can refactor DB operation to a pkg and add test cases for config later.
Check List
Tests
max_allowed_packet
in DM-worker's config and task's configSide effects