State of the art re: group default privileges

From: Michael Orlitzky <michael(at)orlitzky(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: State of the art re: group default privileges
Date: 2013-03-20 20:04:05
Message-ID: 514A1635.1050203@orlitzky.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm running into this exact situation:

http://www.postgresql.org/message-id/CAG1_KcBFM0e2buUG=o7OjQ_KtadrzDGd45jU7Gke3dUZ0Sz92g@mail.gmail.com

We really need to be able to have a group of developers who can create
things and modify each others' stuff[1]. Is it still more or less
impossible?

The workaround that comes to mind is a script to enumerate all
"developers" and then set the defaults one at a time. This breaks
however when we add a new developer -- he can't access any of the
existing stuff.

[1] WITHOUT making them set their own permissions. For the sake of the
discussion, let's say they can't be trusted to get it right, or more
likely, don't feel like it.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martín Marqués 2013-03-20 20:12:44 Re: Can't terminate hung COPY
Previous Message David Rees 2013-03-20 19:37:37 Can't terminate hung COPY