Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] plperl Safe restrictions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: John Hansen <john(at)geeknet(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] plperl Safe restrictions
Date: 2004-11-16 23:40:01
Message-ID: 419A8FD1.6000206@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches

John Hansen wrote:

>>Applied, with changes to allow srand and disallow sprintf, as per
>>subsequent discussion.
>>    
>>
>
>How about allowing: 
>
>use utf8;
>use locale;
>
>?
>
>
>  
>

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.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: John HansenDate: 2004-11-16 23:46:21
Subject: Re: [PATCHES] plperl Safe restrictions
Previous:From: subhashDate: 2004-11-16 23:33:37
Subject: Problems with output function of new datatype!

pgsql-patches by date

Next:From: John HansenDate: 2004-11-16 23:46:21
Subject: Re: [PATCHES] plperl Safe restrictions
Previous:From: Peter EisentrautDate: 2004-11-16 22:57:10
Subject: Re: Updated french translations for 8.0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group