Skip to content
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

sql: improve kill's description #6233

Merged
merged 11 commits into from
Aug 27, 2021
Prev Previous commit
Next Next commit
sql: improve kill's description
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
  • Loading branch information
hawkingrei authored and TomShawn committed Aug 24, 2021
commit 596ffb075c31d2df298dbf7b1cf0445e35386b8f
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.
hawkingrei marked this conversation as resolved.
Show resolved Hide resolved
hawkingrei marked this conversation as resolved.
Show resolved Hide resolved

## See also

Expand Down