From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bricklen Anderson <banderson(at)presinet(dot)com>, Marc Evans <Marc(at)SoftwareHackery(dot)Com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: plperl exception catching |
Date: | 2006-12-13 22:10:59 |
Message-ID: | 20061213221059.GH15546@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 13, 2006 at 05:04:42PM -0500, Tom Lane wrote:
> Bricklen Anderson <banderson(at)presinet(dot)com> writes:
> > Marc Evans wrote:
> >> OK, I must be missing something obvious:
> >> ERROR: creation of Perl function failed: 'eval "string"' trapped by
> >> operation mask at line 2.
>
> > Try as plperlu
>
> This brings up the question of whether it'd be safe to allow eval in
> plperl functions. I'm not sure why it's excluded now ... does it allow
> access to untrusted operations?
ISTM there being something about the Safe module in perl not being able
to enable eval while staying "safe", so to speak.
Looking at the safe module it looks like you can exclude certain
functions from restrictions. The manpage has an example, so a simple
try/catch mechanism could be created if enabling "eval" directly isn't
ok.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Ben | 2006-12-13 22:23:47 | Re: a question for the way-back machine |
Previous Message | Martijn van Oosterhout | 2006-12-13 22:05:52 | Re: a question for the way-back machine |