Why Does the Root User Not Have the Super Permission?

Most relational database cloud service platforms do not provide the super permission for the root user. The super permission allows users to execute many management commands, such as reset master, set global, kill, and reset slave. These operations may cause primary/standby replication errors. To ensure stable running of DB instances, RDS does not provide the super permission for the root user.

If you require the super permission, RDS can provide service capabilities or use other methods to bypass the super permission constraints.

For example:

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

   set global parameter name=Parameter value;

   If the script contains the set global command and causes the super permission loss, 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 the super permission. 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 Creating and Deleting a Plugin.