Skip to content

Commit

Permalink
sql: improve kill's description
Browse files Browse the repository at this point in the history
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
  • Loading branch information
hawkingrei authored and TomShawn committed Aug 24, 2021
1 parent bd3500a commit 596ffb0
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions sql-statements/sql-statement-kill.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,9 @@ Query OK, 0 rows affected (0.00 sec)

## MySQL compatibility

* By design, this statement 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.
* The `KILL TIDB` statement is a TiDB extension. If you are certain that the session you are attempting to kill is on the same TiDB server, set [`compatible-kill-query = true`](/tidb-configuration-file.md#compatible-kill-query) in your configuration file.
* 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.
* You can use `KILL` statment If you are certain that the session you are attempting to kill is on the same TiDB server and set [`compatible-kill-query = true`](/tidb-configuration-file.md#compatible-kill-query) in your configuration file.
* The `KILL TIDB` statement is a TiDB extension. You can kill the session without limitation.

## See also

Expand Down

0 comments on commit 596ffb0

Please sign in to comment.