| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken |
| Date: | 2013-04-29 17:04:11 |
| Message-ID: | 517EA80B.2050403@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/29/2013 09:59 AM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> This moves the general brokenness of this feature from a bug to (a) a
>> documentation issue and (b) unusably fussy. For (a), I think we need
>> the following line in the docs:
>
>> DEFAULT PRIVILEGES may only be granted to a ROLE which already has
>> CREATE permission on the specified schema.
>
> As I pointed out to you last night, it does already say that.
> I think the problem here is that we're just throwing a generic
> permissions failure rather than identifying the particular permission
> needed.
Yeah, a better error message would help a lot. My first thought was
"WTF? I'm the superuser, whaddya mean, 'permission denied'"?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-04-29 17:25:47 | Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken |
| Previous Message | Tom Lane | 2013-04-29 16:59:18 | Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken |