From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Jim Buttafuoco <jim(at)contactbda(dot)com>, 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 'PostgreSQL-development' <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] WIP 2 interpreters for plperl |
Date: | 2006-11-21 10:13:57 |
Message-ID: | 20061121101357.GA7205@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, Nov 20, 2006 at 04:14:34PM -0500, Andrew Dunstan wrote:
> Jim Buttafuoco wrote:
> >I might be one of the ones who depends on the same interpreter. In your
> >new
> >scheme, the _SHARED hash will only be shared between like interpreters,
> >correct? This is going to force me to switch all of my perl code to use
> >the
> >plperlu interpreter :(
>
> Yes. Sorry, but I can't see any way around it. If anyone can suggest one
> then speak up loudly ASAP.
Since the stuff plperlu should be small and self contained, you just
need to set it up so all the data needed by the plperlu function is
passed as a parameter. I suppose we'd need to look at the use case to
see if this is a real obsticle.
I suppose you're not permitted to call other perl functions directly
with \%_SHARED as a parameter, right?
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 | Martijn van Oosterhout | 2006-11-21 10:29:45 | Re: [HACKERS] Client SSL validation using root.crt |
Previous Message | Heikki Linnakangas | 2006-11-21 10:09:40 | Re: XA support (distributed transactions) |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-11-21 14:04:58 | Re: [PATCHES] WIP 2 interpreters for plperl |
Previous Message | Tatsuo Ishii | 2006-11-21 06:44:12 | Re: [PATCHES] replication docs: split single vs. |