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.

Sign up for GitHub

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
Merged

sql: improve kill's description #6233

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
4012054
sql: improve kill's description
hawkingrei Aug 24, 2021
596ffb0
sql: improve kill's description
hawkingrei Aug 24, 2021
7e3e9fe
Update sql-statements/sql-statement-kill.md
hawkingrei Aug 25, 2021
651e771
sql: improve kill's description
hawkingrei Aug 25, 2021
99b7906
sql: improve kill's description
hawkingrei Aug 25, 2021
c904b67
Update sql-statements/sql-statement-kill.md
hawkingrei Aug 25, 2021
e3d0201
mysql_test: support alter table TABLE_NAME engine=xxxx
hawkingrei Aug 25, 2021
2d9c57f
mysql_test: support alter table TABLE_NAME engine=xxxx
hawkingrei Aug 25, 2021
33b6082
Update sql-statements/sql-statement-kill.md
hawkingrei Aug 26, 2021
5b7a608
Update sql-statements/sql-statement-kill.md
hawkingrei Aug 26, 2021
d65cf96
Update sql-statements/sql-statement-kill.md
hawkingrei Aug 26, 2021
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
Prev Previous commit
Next Next commit
Update sql-statements/sql-statement-kill.md 
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
  • Loading branch information
@hawkingrei @TomShawn
hawkingrei and TomShawn authored Aug 26, 2021
commit 5b7a60803adff65838d56c600e6f23997945d9a1
2 changes: 1 addition & 1 deletion sql-statements/sql-statement-kill.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,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.
* Only set [`compatible-kill-query = true`](/tidb-configuration-file.md#compatible-kill-query) in your configuration file if you are certain that clients always will be connected to the same TiDB node, since the default mysql client on ctrl-c will open a new connection to kill the currently running command, and if there are proxies in between, the new connection might be routed to a different TiDB node possibly killing a different session.
hawkingrei marked this conversation as resolved.
Show resolved Hide resolved
* The `KILL TIDB` statement is a TiDB extension. This is different syntax than the mysql `KILL [CONNECTION|QUERY]` command and the mysql command line `ctrl-c` feature, but is safe to use in the same TiDB node.
* 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 <kbd>ctrl</kbd>+<kbd>c</kbd> feature. It is safe to use `KILL TIDB` on the same TiDB node.

## See also

Expand Down