Skip to content

Introduce a new privilege for the set config statement #826

@qw4990

Description

@qw4990

Feature Request

Describe the feature you'd like:

After #768, we can use set config on TiDB to update configs of TiKV/PD.
Now the privilege of this statement is PrivSuper, which is not appropriate.
We should introduce a new privilege for it.

Describe alternatives you've considered:

No

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions