Wanting to learn about pgsql design decision

From: Tal Walter <talw(at)sqreamtech(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Wanting to learn about pgsql design decision
Date: 2016-08-02 08:13:08
Message-ID: CAOFcXYosvsJtCmcW60k6hqB+PFn4HWX6QMrbrm1pa=WR7H24Qw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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!

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2016-08-02 08:40:29 Re: Reviewing freeze map code
Previous Message Kyotaro HORIGUCHI 2016-08-02 07:41:05 Re: asynchronous and vectorized execution