Re: GRANT ON ALL IN schema

From: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
To: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Cc: Petr Jelinek <pjmodos(at)pjmodos(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: GRANT ON ALL IN schema
Date: 2009-06-17 16:45:48
Message-ID: 00E32148-189B-45CA-ADA9-2454AEBE50B5@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Isn't the answer to grant permissions to a role and then just put
people in that role?

--
Greg

On 17 Jun 2009, at 17:25, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
wrote:

> 2009/6/17 Petr Jelinek <pjmodos(at)pjmodos(dot)net>:
>> I agree that Default ACLs are more important and I already offered
>> Stephen
>> help on that. But I've seen countless requests for granting on all
>> tables to
>> a user and I already got some positive feedback outside of the
>> list, so I
>> believe there is demand for this. Also to paraphrase you Tom, by
>> that logic
>> you can tell people to write half of administration functionality
>> as plpgsql
>> functions.
>
> Indeed.
>
> How to do default ACLs and wildcards for GRANT is by far the most
> common question asked by our customers. And they don't understand why
> it's not by default in PostgreSQL.
>
> Installing a script/function for that on every database is just
> painful.
>
> --
> Guillaume
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-06-17 16:49:52 Re: Named transaction
Previous Message Greg Stark 2009-06-17 16:41:53 Re: Named transaction