Skip site navigation (1) Skip section navigation (2)

Re: WIP 2 interpreters for plperl

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: WIP 2 interpreters for plperl
Date: 2006-11-05 22:25:49
Message-ID: 454E64ED.80500@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches

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

Attachment: perldiff
Description: text/plain (16.0 KB)

In response to

Responses

pgsql-hackers by date

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

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group