Postgres app create role8/3/2023 ![]() Update after re-trying the alter default privilegs. So.Is there a command that I can run before or after I create the tables from the application which will ensure that the owner of the database can access the tables within the database? I have been able to solve this before by running the following from the application account: GRANT ALL privileges ON ALL TABLES IN SCHEMA public to rds_superuser īut it seems hacky to have a subordinate user grant privs back to an administrative user. ![]() ![]() My issue is that I cannot use my administrative (rootish) log in to run queries because that user has no privileges on the table. When the app connects (with the master_application credentials) it creates (and therefore owns) the tables. I updated this script to reflect suggestions by Craig Ringer regarding how I should be handling this. GRANT ALL ON DATABASE master_integration TO GROUP master_application ĪLTER DEFAULT PRIVILEGES GRANT INSERT, SELECT, UPDATE, DELETE, TRUNCATE, REFERENCES, TRIGGER ON TABLES TO rds_superuser GRANT ALL ON DATABASE master_integration TO GROUP rds_superuser WITH GRANT OPTION I am creating a database and user for the application as follows: create database master_integration ĬREATE ROLE master_application LOGIN ENCRYPTED PASSWORD '.' VALID UNTIL 'infinity' I have a 'root' user that I have configured with Amazon.Īmazon automatically creates the group role 'rds_superuser' which is very privileged, but not actually a superuser. ![]() What command should I issue to enable a database owner to allow it to access tables in this database and can this be done from that owner's account? ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |