Re: [PATCH] untrusted plperl - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] untrusted plperl
Date
Msg-id 4021.992748055@sss.pgh.pa.us
Whole thread Raw
In response to [PATCH] untrusted plperl  (Alex Pilosov <alex@pilosoft.com>)
Responses Re: [PATCH] untrusted plperl  (Alex Pilosov <alex@pilosoft.com>)
List pgsql-hackers
Alex Pilosov <alex@pilosoft.com> writes:
> Hope someone finds that useful and maybe even merged :)

It looks great to me (except you forgot the documentation updates ;)).
But it'd be nice to get a Perl expert to comment on the thing,
particularly on the safe/unsafe-in-one-interpreter business.

One thought that comes to mind: seems like it'd be possible to
communicate via Perl global variables, functions, etc between
safe and unsafe functions.  This might be good, or it might be
a vehicle for bypassing the safety restrictions.  We should
think hard about that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] inet << indexability (take 3)
Next
From: ncm@zembu.com (Nathan Myers)
Date:
Subject: Re: Doing authentication in backend