This is a discussion on Re: [PATCHES] WIP 2 interpreters for plperl within the pgsql Hackers forums, part of the PostgreSQL category; --> On Mon, Nov 20, 2006 at 04:14:34PM -0500, Andrew Dunstan wrote: > Jim Buttafuoco wrote: > >I might be ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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@svana.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFYtFlIB7bNG8LQkwRAjZIAJ9ybocw/dvWby0yyZ+8oMA4b8eZkQCfZ18h E7XqSukp4Lf7CjSJvbmrqN8= =Vd4g -----END PGP SIGNATURE----- |