Hi everyone!
Today's post is about Postgres SQL.
In my environment we are using Postgres SQL as one option for the backend of AWS (Amazon Web Services).
That's right. We also have another option - MySQL.
This post however will focus on the Postgres SQL error:
"ERROR: must be owner of database databaseName"
Scenario:
I encountered this error when I was trying to drop a database from an AWS cluster.
Amazon allows you to group databases inside of containers. These containers still have the same logic as SQL schemas which hold our database in SQL server.
You can read more about AWS clusters here .
Solution:
This is very easy. It's in the error. All I have to do is make myself the owner of the database so I can delete the database.
I. If your user account does not already have read/write privileges, then you will need to sign in to the Postgres cluster with an admin account so you can grant read/write access to your user account.
II. If your user account does have read/write privileges, then you will be able to alter the database inside the cluster and assign yourself as the owner OR you could do it with the admin user account in step 1.
Note: Run the command below from a different database that is inside the same cluster as the database you would like to change ownership for.
ALTER DATABASE databaseName OWNER TO userName;
If you need to read further on granting permissions in Postgres, please check out this previous post here.
You're all set!
If you have any questions related to this post, please put them below.
Thank you and Happy reading,
-marshé hutchinson
#learnSQLwithme
Today's post is about Postgres SQL.
In my environment we are using Postgres SQL as one option for the backend of AWS (Amazon Web Services).
That's right. We also have another option - MySQL.
This post however will focus on the Postgres SQL error:
"ERROR: must be owner of database databaseName"
Scenario:
I encountered this error when I was trying to drop a database from an AWS cluster.
Amazon allows you to group databases inside of containers. These containers still have the same logic as SQL schemas which hold our database in SQL server.
You can read more about AWS clusters here .
Solution:
This is very easy. It's in the error. All I have to do is make myself the owner of the database so I can delete the database.
I. If your user account does not already have read/write privileges, then you will need to sign in to the Postgres cluster with an admin account so you can grant read/write access to your user account.
II. If your user account does have read/write privileges, then you will be able to alter the database inside the cluster and assign yourself as the owner OR you could do it with the admin user account in step 1.
Note: Run the command below from a different database that is inside the same cluster as the database you would like to change ownership for.
ALTER DATABASE databaseName OWNER TO userName;
If you need to read further on granting permissions in Postgres, please check out this previous post here.
You're all set!
If you have any questions related to this post, please put them below.
Thank you and Happy reading,
-marshé hutchinson
#learnSQLwithme
Comments
Post a Comment