From: | "Mark Hollomon" <mhh(at)nortelnetworks(dot)com> |
---|---|
To: | Jan Wieck <jwieck(at)debis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] plperl intial pass |
Date: | 1999-07-26 13:59:54 |
Message-ID: | 379C69DA.47240D1@americasm01.nt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck wrote:
>
> Mark Hollomon wrote:
>
> >
> > It is not 'safe'.
> >
> > Perl XS modules cannot be used.
>
> What's an XS module? If it's a shared object dynamically
> linked - don't care too much - PL/Tcl cannot either.
Correct. The problem is that the Opcode module, which allows you to
disable features of the compiler (to close security holes) is an
XS module. In theory, it is possible to do without Opcode, but
doing so would create a very heavy perl version dependency in plperl.
So, I have to get XS stuff working in order to disallow XS stuff.
sigh.
And plperl can never be trusted until I can forbid writing to the
filesystem.
>
> >
> > Using Perl in rules hasn't even been thought about.
>
> If a function works from a query, the same function must work
> too in a rule because the rewriter only mangles up parsetrees
> so when executing, they are invoked from a query. Or did you
> mean triggers?
Ick. Correct. I meant triggers.
--
Mark Hollomon
mhh(at)nortelnetworks(dot)com
ESN 451-9008 (302)454-9008
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 1999-07-26 14:20:08 | Re: [HACKERS] postgres Web problem |
Previous Message | Tom Lane | 1999-07-26 13:58:59 | Re: [HACKERS] RE: [INTERFACES] Re: SSL patch |