| From: | Bryn Jeffries <bryn(dot)jeffries(at)sydney(dot)edu(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Irreversible SET ROLE |
| Date: | 2014-12-02 00:50:58 |
| Message-ID: | 7DAF466372B27747B8EA808BE5651FA561BB2594@ex-mbx-pro-01 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote
>> I have a question about preventing SET ROLE from being reset within a session.
>
> You can't; per SQL standard, SET ROLE NONE is supposed to do exactly that.
>
> I think you might be able to do something with invoking untrusted code
> inside a SECURITY DEFINER function. That context disables both SET ROLE
> and SET SESSION AUTHORIZATION. I would not want to bet a lot on that
> being bulletproof, however.
Me neither. But out of interest, do you know what the intent was for the SESSION and LOCAL modifiers for SET ROLE?
Both seem to do nothing more than regular SET ROLE, but are PostgreSQL extensions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Jeffries | 2014-12-02 00:52:00 | Re: Irreversible SET ROLE |
| Previous Message | David G Johnston | 2014-12-02 00:49:41 | Re: Merge rows based on Levenshtein distance |