| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function |
| Date: | 2025-07-31 15:54:27 |
| Message-ID: | CAFCRh--ZOeWP6euXdXz=yri3-5V0wFHXTd2KGLb+UaTUR7k_LQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jul 31, 2025 at 4:13 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 7/31/25 04:37, Dominique Devienne wrote:
> So the below from the original post was not correct:
>
> "My setup ensures that the role I SET LOCAL ROLE to, has (indirectly)
> been granted DMLs on that table."
Not so. DML is Data Modification Language.
I did grant INSERT, UPDATE, DELETE.
As opposed to DQL, Data Query Language.
And yes, I failed to grant SELECT.
Normally SELECT comes from yet another role.
But not in this specific case.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2025-07-31 15:59:42 | Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function |
| Previous Message | Adrian Klaver | 2025-07-31 15:45:46 | Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function |