From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Kenaniah Cerny <kenaniah(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: allow database-specific role memberships |
Date: | 2021-10-11 15:44:20 |
Message-ID: | CAKFQuwaCeF-qZab5RVKQZMQT11gkATtwcjKWf-VYGdu6w5D9OA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday, October 11, 2021, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> I don't think "just don't grant access to those other databases"
> is actually a proper answer- there is certainly a use-case for "I want
> user X to have read access to all tables in *this* database, and also
> allow them to connect to some other database but not have that same
> level of access there."
>
Sure, that has a benefit. But creating a second user for the other
database and putting the onus on the user to use the correct credentials
when logging into a particular database is a valid option - it is in fact
the status quo. Due to the complexity of adding a whole new grant
dimension to the system the status quo is an appealing option. Annoyance
factor aside it technically solves the per-database permissions problem put
forth.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-10-11 15:47:55 | Re: Corruption with IMMUTABLE functions in index expression. |
Previous Message | Fujii Masao | 2021-10-11 15:29:03 | Re: Inconsistency in startup process's MyBackendId and procsignal array registration with ProcSignalInit() |