Re: Wanting to learn about pgsql design decision

Thanks Tom and Andrew!
This is indeed interesting.

Because I have a couple more of these questions, and I prefer to avoid
receiving a RTFM,
I'd appreciate if you could help me understand how I can research the
answers to these type of questions by myself.

The example questions I gave are just some of the questions I've tried to
search the answer to, using google and searching this mailing list
specifically, but I came up with nothing. Could I perhaps search the commit
comments somehow? Or perhaps a different approach to suggest?

Thanks for the interesting comments and help!

On Tue, Aug 2, 2016 at 7:43 PM, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
wrote:

> >>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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)
>