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

system-variables: add skip-name-resolve #6491

Merged
merged 2 commits into from
Sep 30, 2021
Merged
Changes from 1 commit
Commits
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
17 changes: 17 additions & 0 deletions system-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -212,6 +212,23 @@ mysql> SELECT * FROM t1;
- Range: `[0, 65535]`
- The port that the `tidb-server` is listening on when speaking the MySQL protocol.

### skip_name_resolve <span class="version-mark">New in v5.2.0</span>

- Scope: GLOBAL
- Default value: `OFF`
- This controls if the `tidb-server` should resolve hostnames as part of the connection handshake.
dveeden marked this conversation as resolved.
Show resolved Hide resolved
- Enabling this option is useful as a performance optimization when DNS is unreliable.
dveeden marked this conversation as resolved.
Show resolved Hide resolved

> **Note:**
>
> When `skip_name_resolve=ON`, users with a hostname in their identity will no longer be able to log in. i.e.
dveeden marked this conversation as resolved.
Show resolved Hide resolved
>
> ```sql
> CREATE USER 'appuser'@'apphost' IDENTIFIED BY 'app-password';
> ```
>
> In this example, it is recommended to replace _apphost_ with an IP address or wildcard (`%`).
dveeden marked this conversation as resolved.
Show resolved Hide resolved

### socket

- Scope: NONE
Expand Down