Re: [PATCH] untrusted plperl

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alex Pilosov <alex(at)pilosoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] untrusted plperl
Date: 2001-06-17 03:20:55
Message-ID: 4021.992748055@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alex Pilosov <alex(at)pilosoft(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Myers 2001-06-17 09:58:09 Re: Doing authentication in backend
Previous Message Jason Tishler 2001-06-17 02:10:27 Re: [current] readline breakage