From 92bbd7a1aa34bf14dc1f54502774553ab4a0dcb5 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Fri, 3 Sep 2021 10:18:14 +0800 Subject: [PATCH] sql: fix the correctness problem about kill (#6377) (#6378) --- sql-statements/sql-statement-kill.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql-statements/sql-statement-kill.md b/sql-statements/sql-statement-kill.md index b80a04de3c234..20a1f4414ca5a 100644 --- a/sql-statements/sql-statement-kill.md +++ b/sql-statements/sql-statement-kill.md @@ -35,7 +35,7 @@ Query OK, 0 rows affected (0.00 sec) * By design, `KILL` is not compatible with MySQL by default. This helps prevent against a case of a connection being terminated on the wrong TiDB server, because it is common to place multiple TiDB servers behind a load balancer. * DO NOT set [`compatible-kill-query = true`](/tidb-configuration-file.md#compatible-kill-query) in your configuration file UNLESS you are certain that clients will be always connected to the same TiDB node. This is because pressing ctrl+c in the default MySQL client opens a new connection in which `KILL` is executed. If there are proxies in between, the new connection might be routed to a different TiDB node, which possibly kills a different session. -* The `KILL TIDB` statement is a TiDB extension, which is a different syntax from the MySQL `KILL [CONNECTION|QUERY]` command and the MySQL command-line ctrl+c feature. It is safe to use `KILL TIDB` on the same TiDB node. +* The `KILL TIDB` statement is a TiDB extension. The feature of this statement is similar to the MySQL `KILL [CONNECTION|QUERY]` command and the MySQL command-line ctrl+c feature. It is safe to use `KILL TIDB` on the same TiDB node. ## See also