Re: Wanting to learn about pgsql design decision - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Wanting to learn about pgsql design decision
Date
Msg-id 87shungmwf.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Wanting to learn about pgsql design decision  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Wanting to learn about pgsql design decision  (Tal Walter <talw@sqreamtech.com>)
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>> - Why to read from a table, both a usage permission on the schema>> and a read access permission on the table is
needed?
Tom> Because the SQL standard says so.

You'd think, but in fact it doesn't; the spec (at least 2008 and the
2011 drafts) has no concept of grantable permissions on schemas, and
ties table ownership and schema ownership together.

(See the definition of <privileges> to see that there's nothing there
for schemas, and the definition of <table definition> for the fact that
it's the schema owner who also owns the table and gets the initial
grants on it, and <drop table statement> and <alter table statement> to
confirm that only the schema owner can alter or drop the table. The
access rules for <table reference> only require permission on a table
column, no mention of schemas.)

-- 
Andrew (irc:RhodiumToad)



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: PATCH: two slab-like memory allocators
Next
From: Bruce Momjian
Date:
Subject: Re: pg_size_pretty, SHOW, and spaces