From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Michael Orlitzky *EXTERN*" <michael(at)orlitzky(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: (Default) Group permissions |
Date: | 2013-07-01 07:36:11 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17BC24EE@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Orlitzky wrote:
> We use Postgres for shared hosting; i.e. what most people use MySQL for.
> The biggest headache for us so far has been that we're unable to get
> group permissions set up effectively so that different groups of
> customers, admins, apaches, etc. can access/modify the data they need,
> without manual intervention from someone with root and a relatively deep
> knowledge of the permissions system.
>
> I posted about this a while ago, and I promised to step back and come up
> with an example of the type of situation I'm talking about. It's not
> perfect, but if I don't post it now, it'll never get finished:
>
> https://github.com/mjorlitzky/postgres-groups
I took a look, but it takes more time than I'm willing to spend
to actually get to your problem.
Could you outline briefly what the problem is?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-07-01 07:54:00 | Re: Application locking |
Previous Message | Andrew Sullivan | 2013-07-01 01:56:39 | Re: (Default) Group permissions |