I wrote:
>
> I have made some progress with what I think is needed to have two 
> interpreters for plperl. This is a lot harder than the pltcl case for 
> two reasons: 1. there are no restrictions on having 2 tcl 
> interpreters, and 2. tcl does not need to save and restore context as 
> we have to do with perl. I think I have a conceptual siolution to 
> these two problems, but what I have is currently segfaulting somewhat 
> myteriously. Tracing a dynamically loaded library in a postgres 
> backend with a debugger is less than fun, too. I am attaching what I 
> currently have, liberally sprinkled with elog(NOTICE) calls as trace 
> writes.
>
>

With a little more perseverance I found the problem. The attached patch 
passes regression. But it now needs plenty of eyeballs and testing.

cheers

andrew

In response to

• WIP 2 interpreters for plperl at 2006-11-05 21:14:17 from Andrew Dunstan

Responses

• Re: [PATCHES] WIP 2 interpreters for plperl at 2006-11-12 16:03:49 from Andrew Dunstan

pgsql-hackers by date

Next:	From: Guillaume Lelarge	Date: 2006-11-05 22:47:32
	Subject: Re: NULL in arrays
Previous:	From: Simon Riggs	Date: 2006-11-05 22:03:48
	Subject: Re: Writing WAL for relcache invalidation:pg_internal.init

pgsql-patches by date

Next:	From: Tom Lane	Date: 2006-11-05 23:42:27
	Subject: Re: Writing WAL for relcache invalidation:pg_internal.init
Previous:	From: Simon Riggs	Date: 2006-11-05 22:03:48
	Subject: Re: Writing WAL for relcache invalidation:pg_internal.init