| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Cosimo Simeone <cosimo(dot)simeone(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Need help understanding has_function_privilege |
| Date: | 2025-03-23 14:50:21 |
| Message-ID: | CAKFQuwZmXG7uKX0dH+5=RMHrpTkGXa-VG4gePAOTtP+vd+C=ig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday, March 21, 2025, Cosimo Simeone <cosimo(dot)simeone(at)gmail(dot)com> wrote:
> Hi, and thanks (both of you!)
> Shouldn't the
> create role my_user NOINHERIT;
> avoid this? And since not, why? :-)
>
>
We might need to improve documentation surrounding the public pseudo-role a
bit. Since it’s not a true group role I suspect inherit/noinherit doesn’t
apply. (You also cannot SET to it, nor admin it - not tested.) Losing the
execute privilege on every built-in function would be way too annoying.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-03-23 15:37:11 | Re: Experience and feedback on pg_restore --data-only |
| Previous Message | David Rowley | 2025-03-23 13:35:58 | Re: Querying one partition in a function takes locks on all partitions |