Re: First feature patch for plperl - draft [PATCH]

From: Jeff <threshar(at)torgo(dot)978(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff <threshar(at)threshar(dot)is-a-geek(dot)com>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: First feature patch for plperl - draft [PATCH]
Date: 2009-12-04 18:51:53
Message-ID: D5304934-DE14-4171-80BD-4CEFF7B35FCB@torgo.978.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Dec 4, 2009, at 1:44 PM, Andrew Dunstan wrote:

>
> As is documented, all you have to do is have:
>
> custom_variable_classes = 'plperl'
> plperl.use_strict = 'true'
>
> in your config. You only need to put the documented BEGIN block in
> your function body if you want to do use strict mode on a case by
> case basis.
>
> We can't allow an unrestricted "use strict;" in plperl functions
> because it invokes an operation (require) that Safe.pm rightly
> regards as unsafe.
>

Yeah, saw that in the manual in the plperl functions & arguments page
(at the bottom).
I think my confusion came up because I'd read the trust/untrusted
thing which removes the ability to use use/require.

Maybe a blurb or moving that chunk of doc to the trusted/untrusted
page might make that tidbit easier to find?

--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-12-04 18:56:14 Re: First feature patch for plperl - draft [PATCH]
Previous Message Tom Lane 2009-12-04 18:51:00 Re: First feature patch for plperl - draft [PATCH]