-
Notifications
You must be signed in to change notification settings - Fork 678
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.
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
system-variables: update from generated source #6838
Changes from all commits
41ccb8f
c05a84c
066dc0a
2697c92
c4e5e5e
e648b47
00ee361
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -294,10 +294,10 @@ This variable is an alias for `last_insert_id`. | |
> | ||
> Unlike in MySQL, the `max_execution_time` system variable currently works on all kinds of statements in TiDB, not only restricted to the `SELECT` statement. The precision of the timeout value is roughly 100ms. This means the statement might not be terminated in accurate milliseconds as you specify. | ||
### placement_checks | ||
### placement_checks <span class="version-mark">New in v5.3.0</span> | ||
|
||
- Scope: SESSION | GLOBAL | ||
- Default value: ON | ||
- Default value: `ON` | ||
- This variable controls whether DDL statements validate [Placement Rules in SQL](/placement-rules-in-sql.md). | ||
- It is intended to be used by logical dump/restore tools to ensure that tables can always be created even if placement rules are violated. This is similar to how mysqldump writes `SET FOREIGN_KEY_CHECKS=0;` to the start of every dump file. | ||
|
||
|
@@ -411,6 +411,7 @@ This variable is an alias for `last_insert_id`. | |
### tidb_allow_function_for_expression_index <span class="version-mark">New in v5.2.0</span> | ||
- Scope: NONE | ||
- Default value: `lower, md5, reverse, upper, vitess_hash` | ||
- This variable is used to show the functions that are allowed to be used for creating expression indexes. | ||
### tidb_allow_mpp <span class="version-mark">New in v5.0</span> | ||
|
@@ -845,14 +846,14 @@ Query OK, 0 rows affected (0.09 sec) | |
- Default value: `ON` | ||
- This variable is used to dynamically control whether the telemetry collection in TiDB is enabled. By setting the value to `OFF`, the telemetry collection is disabled. If the [`enable-telemetry`](/tidb-configuration-file.md#enable-telemetry-new-in-v402) TiDB configuration item is set to `false` on all TiDB instances, the telemetry collection is always disabled and this system variable will not take effect. See [Telemetry](/telemetry.md) for details. | ||
### tidb_enable_tso_follower_proxy <span class="version-mark">New in v5.3</span> | ||
### tidb_enable_tso_follower_proxy <span class="version-mark">New in v5.3.0</span> | ||
- Scope: GLOBAL | ||
- Default value: `OFF` | ||
- This variable is used to enable the TSO Follower Proxy feature. When the value is `OFF`, TiDB only gets TSO from the PD leader. After this feature is enabled, TiDB gets TSO by evenly sending requests to all PD nodes and forwarding TSO requests through PD followers. This helps reduce the CPU pressure of PD leader. | ||
- Scenarios for enabling TSO Follower Proxy: | ||
* Due to the high pressure of TSO requests, the CPU of the PD leader reaches a bottleneck, which causes high latency of TSO RPC requests. | ||
* The TiDB cluster has many TiDB instances, and increasing the value of [`tidb_tso_client_batch_max_wait_time`](#tidb_tso_client_batch_max_wait_time-new-in-v53) cannot alleviate the high latency issue of TSO RPC requests. | ||
* The TiDB cluster has many TiDB instances, and increasing the value of [`tidb_tso_client_batch_max_wait_time`](#tidb_tso_client_batch_max_wait_time-new-in-v530) cannot alleviate the high latency issue of TSO RPC requests. | ||
> **Note:** | ||
> | ||
|
@@ -1130,10 +1131,11 @@ For a system upgraded to v5.0 from an earlier version, if you have not modified | |
- Default value: `tikv,tiflash,tidb` | ||
- This variable is used to set the storage engine list that TiDB can use when reading data. | ||
### tidb_log_file_max_days <span class="version-mark">New in v5.3</span> | ||
### tidb_log_file_max_days <span class="version-mark">New in v5.3.0</span> | ||
- Scope: SESSION | ||
- Default value: `0` | ||
- Range: `[0, 2147483647]` | ||
- This variable is used to adjust the maximum days of logger on the current TiDB instance. Its value defaults to the value of the [`max-days`](/tidb-configuration-file.md#max-days) configuration in the configuration file. Changing the variable value only affects the current TiDB instance. After TiDB is restarted, the variable value is reset and the configuration value is not affected. | ||
### tidb_low_resolution_tso | ||
|
@@ -1553,7 +1555,7 @@ SET tidb_slow_log_threshold = 200; | |
- Unit: Bytes | ||
- This variable is used to set the maximum size of a single [temporary table](/temporary-tables.md). Any temporary table with a size larger than this variable value causes error. | ||
### tidb_tso_client_batch_max_wait_time <span class="version-mark">New in v5.3</span> | ||
### tidb_tso_client_batch_max_wait_time <span class="version-mark">New in v5.3.0</span> | ||
- Scope: GLOBAL | ||
- Default value: `0` | ||
|
@@ -1626,7 +1628,7 @@ SET tidb_slow_log_threshold = 200; | |
### timestamp | ||
- Scope: SESSION | ||
- Default value: "" | ||
- Default value: `0` | ||
- A non-empty value of this variable indicates the UNIX epoch that is used as the timestamp for `CURRENT_TIMESTAMP()`, `NOW()`, and other functions. This variable might be used in data restore or replication. | ||
### transaction_isolation | ||
|
@@ -1652,22 +1654,22 @@ This variable is an alias for `transaction_isolation`. | |
- Default value: (string) | ||
- This variable returns additional details about the TiDB version. For example, 'TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible'. | ||
### version_compile_os | ||
### version_compile_machine | ||
- Scope: NONE | ||
- Default value: (string) | ||
- This variable returns the name of the OS on which TiDB is running. | ||
- This variable returns the name of the CPU architecture on which TiDB is running. | ||
### version_compile_machine | ||
### version_compile_os | ||
- Scope: NONE | ||
- Default value: (string) | ||
- This variable returns the name of the CPU architecture on which TiDB is running. | ||
- This variable returns the name of the OS on which TiDB is running. | ||
### wait_timeout | ||
- Scope: SESSION | GLOBAL | ||
- Default value: `0` | ||
- Default value: `28800` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We always treat the default value change with extra care. From which version this default value is changed? If it is changed from v5.3.0, shall we let the QA team @seiya-annie know and add it to v5.3.0 release notes? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I took a look at the PR, and it's not cherry picked: pingcap/tidb#29569 It might be worth docs having a script to detect defaults changes. I am not specifically changing the default here - it has already been changed. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Translated into Chinese in pingcap/docs-cn#8076 |
||
- Range: `[0, 31536000]` | ||
- Unit: Seconds | ||
- This variable controls the idle timeout of user sessions. A zero-value means unlimited. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This causes a few broken anchors in release-5.3.0.md. Could you please fix the broken anchors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed :-)