This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
config: adding [tidb] max-allowed-packet
config
#248
Merged
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.
this allows sending rows > 4 MiB when using TiDB backend
What problem does this PR solve?
Expose the
maxAllowedPacket
DSN parameter totidb-lightning.toml
(perhaps we should just accept arbitrary DSNs 🤷♂)What is changed and how it works?
[tidb] max-allowed-packet = 67_108_864
config.Check List
Tests
Side effects
Related changes
tidb-ansible
repository (add the new config to the templates)