From: | Steven Crandell <steven(dot)crandell(at)gmail(dot)com> |
---|---|
To: | Richard Gbs <richardgbs(at)yahoo(dot)com> |
Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Permission issues. Please help |
Date: | 2018-03-14 04:23:45 |
Message-ID: | CALvesgnKgeG3WuWJwOimD0-Gs4HikOaY6A89LK5YvJRUR6HG=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Mar 13, 2018 at 8:52 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Tuesday, March 13, 2018, Richard Gbs <richardgbs(at)yahoo(dot)com> wrote:
>>
>> I need to have user1,2 and 3 have all the same privileges against any
>> obeject in the database created by any of them.
>>
>> Can someone give a high level approach to this please?
>>
>
> Create a group with all three as members. Have them assign ownership of
> created objects to said group.
>
> Maybe not the most secure but should meet your stated goal.
>
> David J.
>
default privileges might also prove useful in making a setup like this
easier to maintain over the long-term.
e.g.
ALTER DEFAULT PRIVILEGES FOR USER user1 IN SCHEMA public GRANT SELECT ON
TABLES TO user2;
YMMV, but something like this would ensure that user2 is automatically
granted SELECT on any tables created by user1 in schema public.
Combine with role inheritance to help cut down on the number of total
default privs required
\ddp to view default privs
From | Date | Subject | |
---|---|---|---|
Next Message | Azimuddin Mohammed | 2018-03-14 05:39:07 | whitelist ip for postgres |
Previous Message | David G. Johnston | 2018-03-14 03:52:39 | Re: Permission issues. Please help |