From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgsql-admin(at)postgresql(dot)org, "Andy Shellam (Mailing Lists)" <andy-lists(at)networkmail(dot)eu>, Kiswono Prayogo <kiswono(at)gmail(dot)com> |
Subject: | Re: Help me understanding the schema |
Date: | 2009-12-05 23:15:13 |
Message-ID: | dcc563d10912051515q74a4a34fnb138bb82a3dc483e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, Dec 5, 2009 at 3:46 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le samedi 5 décembre 2009 à 23:08:58, Andy Shellam (Mailing Lists) a écrit :
>> Hi Scott,
>>
>> >> 7. we can set the privilege of user x for schema y
>> >> ie. database aaa contains schema a1, a2 and a3. user xx can query from
>> >> schema a1 only, user yy can query from schema a2 only?
>> >
>> > No, perms on schemas control schema actions like create. perms on
>> > tables control user access.
>>
>> I thought that a user also had to have the USAGE right on a schema? In an
>> application I'm working on at the moment, it threw the error "permission
>> denied on schema xxx" even if permissions on the tables within the schema
>> were OK - I had to assign the USAGE right on the schema.
>>
>
> You're right. One needs USAGE right to use the schema, and CREATE right to
> create objects in this schema.
I completely missed that in the docs. Thanks for the catch.
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Tucker | 2009-12-07 18:29:18 | Question about replication options |
Previous Message | Guillaume Lelarge | 2009-12-05 22:46:03 | Re: Help me understanding the schema |