Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update tidb_dml_batch_size section #7371

Merged
merged 6 commits into from
Apr 14, 2022
Merged

Update tidb_dml_batch_size section #7371

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
74cafc8
Update tidb_dml_batch_size section
leowangpingcap Jan 7, 2022
f8fb6bb
Update system-variables.md
leowangpingcap Jan 7, 2022
f4437fd
Update system-variables.md
leowangpingcap Jan 7, 2022
0b5275b
Update system-variables.md
leowangpingcap Jan 7, 2022
4665275
Update system-variables.md
leowangpingcap Feb 21, 2022
03f5bf0
Update system-variables.md
TomShawn Mar 9, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 8 additions & 0 deletions system-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -478,6 +478,13 @@ MPP is a distributed computing framework provided by the TiFlash engine, which a

In the case of a poor network environment, appropriately increasing the value of this variable can effectively alleviate error reporting to the application end caused by timeout. If the application end wants to receive the error information more quickly, minimize the value of this variable.

### tidb_batch_insert

- Scope: SESSION
- Default value: `OFF`
- This variable permits `tidb_dml_batch_size` to be used in `INSERT` statements.
- Only the value `OFF` provides ACID compliance. Setting this to any other value breaks the atomicity and isolation guarantees of TiDB, because an individual `INSERT` statement will be split into smaller transactions.

### tidb_broadcast_join_threshold_count <span class="version-mark">New in v5.0</span>

- Scope: SESSION | GLOBAL
Expand Down Expand Up @@ -629,6 +636,7 @@ Constraint checking is always performed in place for pessimistic transactions (d
- Range: `[0, 2147483647]`
- Unit: Rows
- When this value is greater than `0`, TiDB will batch commit statements such as `INSERT` or `LOAD DATA` into smaller transactions. This reduces memory usage and helps ensure that the `txn-total-size-limit` is not reached by bulk modifications.
- To use `tidb_dml_batch_size` in `INSERT` statements, you also need to set the system variable `tidb_batch_insert` to `ON`.
- Only the value `0` provides ACID compliance. Setting this to any other value will break the atomicity and isolation guarantees of TiDB.

### tidb_enable_1pc <span class="version-mark">New in v5.0</span>
Expand Down