| 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 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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 | Content-Type | Size |
|---|---|---|
| perldiff | text/plain | 16.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2006-11-05 22:47:32 | Re: NULL in arrays |
| Previous Message | Simon Riggs | 2006-11-05 22:03:48 | Re: Writing WAL for relcache invalidation:pg_internal.init |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-05 23:42:27 | Re: Writing WAL for relcache invalidation:pg_internal.init |
| Previous Message | Simon Riggs | 2006-11-05 22:03:48 | Re: Writing WAL for relcache invalidation:pg_internal.init |