Re: [HACKERS] plperl Safe restrictions

Поиск
Список
Период
Сортировка
Искать
От
John Hansen
Тема
Re: [HACKERS] plperl Safe restrictions
Дата
Msg-id
1100648780.14124.14.camel@localhost.localdomain
Ответ на
Список
Дерево обсуждения
Re: [HACKERS] plperl Safe restrictions John Hansen <john@geeknet.com.au>
Re: [HACKERS] plperl Safe restrictions Andrew Dunstan <andrew@dunslane.net>
Re: [HACKERS] plperl Safe restrictions John Hansen <john@geeknet.com.au>
Re: [HACKERS] plperl Safe restrictions Bruce Momjian <pgman@candle.pha.pa.us>
Re: [HACKERS] plperl Safe restrictions "Andrew Dunstan" <andrew@dunslane.net>
Re: [HACKERS] plperl Safe restrictions Tom Lane <tgl@sss.pgh.pa.us>
> I think it is *way* too late in the dev cycle to be proposing this. 
> Maybe it should be a TODO item - I at least don't have time even to 
> think about the implications os using these pragmas. The effect of the 
> first is achievable via an environment setting, I believe.
> 
> If you need these badly enough, use plperlu where there are no 
> restrictions to overcome - the big problem is that 'use anything' 
> requires that we enable the 'require' op, and that is certainly not 
> going to happen without a great deal of thought.

Fair enough, was just a suggestion as they seem obviously useful, even
to the non-superuser plperl programmer.

TODO item would suffice :)

... John

В списке pgsql-patches по дате отправления
От: Andrew Dunstan
Дата:
От: Tom Lane
Дата:
Сообщение: Re: Win32 signals & sockets
FAQ