From a8fbd45a7d31e4b72b4195fbd63b55fb9d8c6016 Mon Sep 17 00:00:00 2001 From: Null not nil Date: Mon, 30 Nov 2020 14:43:14 -0700 Subject: [PATCH] system-variables: remove last-plan-from-binding --- system-variables.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/system-variables.md b/system-variables.md index b0975147cf791..01e136dd8f1b7 100644 --- a/system-variables.md +++ b/system-variables.md @@ -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 New in v4.0 - -- 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 @@ -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