Skip to content

sql: clarify description about SET GLOBAL (#22175) #22187

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

Merged
ti-chi-bot merged 4 commits into from
Dec 15, 2025
Merged

sql: clarify description about SET GLOBAL (#22175) #22187

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
82b72b9
Update sql-statement-set-variable.md
hfxsd Dec 15, 2025
9e3238a
Update sql-statement-set-variable.md
hfxsd Dec 15, 2025
e377391
Apply suggestions from code review
hfxsd Dec 15, 2025
53e04d5
Update sql-statements/sql-statement-set-variable.md
hfxsd Dec 15, 2025
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
8 changes: 7 additions & 1 deletion sql-statements/sql-statement-set-variable.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,13 @@ SELECT @myvar, @myvar + 1;

The following behavior differences apply:

* Changes made with `SET GLOBAL` will be propagated to all TiDB instances in the cluster. This differs from MySQL, where changes do not propagate to replicas.
* In MySQL, changes made with `SET GLOBAL` do not apply to replicas. However in TiDB, the scope of `SET GLOBAL` depends on the specific system variable:

* Global variables: for most system variables (for example, those that affect cluster behavior or optimizer behavior), changes made with `SET GLOBAL` apply to all TiDB instances in the cluster.
* Instance-level variables: for some system variables (for example, `max_connections`), changes made with `SET GLOBAL` apply only to the TiDB instance that the current connection is using.

Therefore, when using `SET GLOBAL` to modify a variable, always check the [documentation](/system-variables.md) of that variable, especially the "Persists to cluster" attribute, to confirm the scope of the change.

* TiDB presents several variables as both readable and settable. This is required for MySQL compatibility, because it is common for both applications and connectors to read MySQL variables. For example: JDBC connectors both read and set query cache settings, despite not relying on the behavior.
* Changes made with `SET GLOBAL` will persist through TiDB server restarts. This means that `SET GLOBAL` in TiDB behaves more similar to `SET PERSIST` as available in MySQL 8.0 and above.
* TiDB does not support `SET PERSIST` and `SET PERSIST_ONLY`, because TiDB persists global variables.
Expand Down