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

From Tal Walter
Subject Wanting to learn about pgsql design decision
Date
Msg-id CAOFcXYosvsJtCmcW60k6hqB+PFn4HWX6QMrbrm1pa=WR7H24Qw@mail.gmail.com
Whole thread Raw
Responses Re: Wanting to learn about pgsql design decision  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Dear list,

I'm interested in pgsql, and would like to know more about the design decisions behind it's features.
Where should I search in order to know more about subjects, for example:
  • Why in the roles system, user are actually roles with login attribute and not a separate entity.
  • Why to read from a table, both a usage permission on the schema and a read access permission on the table is needed? Alternatively, there could be a usage permission on schema just to alter the schema itself or add tables to it, and not require it in the case of selecting from a table from inside it.
And other questions of this sort.

Thank you very much!

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: asynchronous and vectorized execution
Next
From: Amit Kapila
Date:
Subject: Re: Reviewing freeze map code