From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Permission Read Only User |
Date: | 2019-03-16 01:02:21 |
Message-ID: | 24342e74-6ab2-97c9-2ac5-e34349ff0b21@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/15/19 6:44 PM, Adrian Klaver wrote:
> On 3/15/19 4:37 PM, Sathish Kumar wrote:
>> Hi All,
>>
>> I have created a read only user to perform select statements on our
>> database but whenever we create new tables on the database this user is
>> unable to view it unless I grant select again for this table. Is there a
>> way I can make select as default permission for this user so that in
>> future if I create any new tables, it will be still accessible.
>
> Maybe this?:
>
> https://www.postgresql.org/docs/11/sql-alterdefaultprivileges.html
That's just what we used.
Create a role READONLY who is granted CONNECT and alter the default
permissions on all your schemas to grant SELECT to that role.
Then create "user" roles which inherit from READONLY.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-03-16 01:43:06 | Re: Conditional INSERT |
Previous Message | Adrian Klaver | 2019-03-16 00:41:20 | Re: Conditional INSERT |