| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Kohei Kaigai <Kohei(dot)Kaigai(at)emea(dot)nec(dot)com> |
| Cc: | Noah Misch <noah(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Subject: | Re: [v9.2] Fix Leaky View Problem |
| Date: | 2011-09-07 13:09:15 |
| Message-ID: | CAA-aLv5X0j_39MgBzp1Dv7twxoadJMdJWTrEgVbu-Or+fN8f_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24 August 2011 13:38, Kohei Kaigai <Kohei(dot)Kaigai(at)emea(dot)nec(dot)com> wrote:
> The (2) is new stuff from the revision in commit-fest 1st. It enables to
> supply "NOLEAKY" option on CREATE FUNCTION statement, then the function is
> allowed to distribute across security barrier. Only superuser can set this
> option.
>
"NOLEAKY" doesn't really sound appropriate as it sounds like pidgin English.
Also, it could be read as "Don't allow leaks in this function". Could we
instead use something like TRUSTED or something akin to it being allowed to
do more than safer functions? It then describes its level of behaviour
rather than what it promises not to do.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2011-09-07 13:10:35 | problem of win32.mak |
| Previous Message | Fujii Masao | 2011-09-07 12:37:52 | Re: Cascaded standby message |