| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allowing to create LEAKPROOF functions to non-superuser |
| Date: | 2021-04-25 19:13:58 |
| Message-ID: | 2007310.1619378038@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andrey Borodin (x4mmm(at)yandex-team(dot)ru) wrote:
>> Customer was restoring pg_dump of on-premise ERP known as 1C (something like TurboTax) with this add-on [0]
> Erm, it's very clearly not leakproof and will happily return information
> about the value passed in during some error cases...
Yeah, that's pretty much a poster-child example for NOT letting
random users fool with leakproofness settings.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-04-25 19:40:40 | Re: Fix dropped object handling in pg_event_trigger_ddl_commands |
| Previous Message | Юрий Соколов | 2021-04-25 18:57:10 | Re: [HACKERS] Cached plans and statement generalization |