Help Center > > FAQs> Database Permission> Why Does the Root User Not Have the Super Permissions?

Why Does the Root User Not Have the Super Permissions?

Updated at: Jul 07, 2021 GMT+08:00

Most relational database cloud service platforms do not provide super permissions for the root user. The super permissions allow users to execute many management commands, such as reset master, set global, kill, and reset slave. These operations may cause primary/standby replication errors. This is a major difference between public cloud databases and on-premises MySQL databases. To ensure stable running of DB instances, RDS does not provide the super permission for the root user.

If you need to perform actions that normally require super permissions, RDS provides alternative methods.

For example:

  1. You can modify parameter values only on the RDS console. You cannot run the following command on an RDS DB database to modify parameter values.

    set global parameter name=Parameter value;

    If the script contains the set global command, delete the set global command and modify parameter values through the RDS console.

  2. An error is reported after you run the following command because the root user does not have super permissions. You can delete definer='root' from the command to solve the problem.

    create definer='root'@'%' trigger(procedure)...

    You can import data using mysqldump. For operation details, see Migrating Data to RDS for MySQL Using mysqldump.

  3. You can create PostgreSQL plugins by referring to Managing a Plugin.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel