RE: Permission issues. Please help - Mailing list pgsql-admin

From Ricardo Martin Gomez
Subject RE: Permission issues. Please help
Date
Msg-id FR1P15201MB229679EBD2138A75796B9C8AA3D10@FR1P15201MB2296.LAMP152.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Permission issues. Please help  (Steven Crandell <steven.crandell@gmail.com>)
List pgsql-admin
Hi, Probably you need to grant permission like this
GRANT SELECT ON ALL TABLES IN SCHEMA public TO user1;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO user2;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO user3;
And just each owner can insert or update 

______________________
Saludos 
Ing. Ricardo Martín Gomez
DBA - SysAdmin

De: Steven Crandell <steven.crandell@gmail.com>
Enviado: miércoles, 14 de marzo de 2018 01:23 a.m.
Para: Richard Gbs
Cc: pgsql-admin@lists.postgresql.org
Asunto: Re: Permission issues. Please help
 


On Tue, Mar 13, 2018 at 8:52 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Tuesday, March 13, 2018, Richard Gbs <richardgbs@yahoo.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

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: whitelist ip for postgres
Next
From: "Heinemann, Manfred (IMS)"
Date:
Subject: Function search_path