Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions system-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,12 +72,6 @@ SET GLOBAL tidb_distsql_scan_concurrency = 10;
- Default value: 0
- This variable is used to show whether the execution plan used in the previous `execute` statement is taken directly from the plan cache.

### last_plan_from_binding <span class="version-mark">New in v4.0</span>

- Scope: SESSION
- Default value: 0
- This variable is used to show whether the execution plan used in the previous statement was influenced by a [plan binding](/sql-plan-management.md)

### max_execution_time

- Scope: SESSION | GLOBAL
Expand All @@ -88,7 +82,7 @@ SET GLOBAL tidb_distsql_scan_concurrency = 10;
>
> 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.

### `interactive_timeout`
### interactive_timeout

- Scope: SESSION | GLOBAL
- Default value: 28800
Expand Down