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

Re: [PATCHES] plperl Safe restrictions

From: John Hansen <john(at)geeknet(dot)com(dot)au>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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:46:21
Message-ID: 1100648780.14124.14.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> 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


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-11-17 00:11:08
Subject: Re: Problems with output function of new datatype!
Previous:From: Andrew DunstanDate: 2004-11-16 23:40:01
Subject: Re: [PATCHES] plperl Safe restrictions

pgsql-patches by date

Next:From: Tom LaneDate: 2004-11-17 00:18:10
Subject: Re: Win32 signals & sockets
Previous:From: Andrew DunstanDate: 2004-11-16 23:40:01
Subject: Re: [PATCHES] plperl Safe restrictions

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