On 24 August 2011 13:38, Kohei Kaigai <kohei.kai...@emea.nec.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
