From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "Mark Dilger" <pgsql(at)markdilger(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: plperl/plperlu interaction |
Date: | 2006-11-10 01:48:30 |
Message-ID: | 1890.24.211.165.134.1163123310.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mark Dilger wrote:
> Tom Lane wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> Anyway, it is probably not expected by many users that loading a
module
>>> in plperlu makes it available to plperl - I was slightly surprised
myself to see it work and I am probably more aware than most of perl
and
>>> plperl subtleties.
>> I think that is a bug and needs to be fixed. We have the precedent of
pltcl, which uses separate interpreters for pltcl and pltclu for
exactly
>> this reason.
>
> If this is fixed, what becomes the mechanism for an administrator to
make
> a perl
> module available to plperl functions? I didn't see any other way to do
this
> documented. Thanks,
>
This isn't documented either :-)
I discovered this when I was working on a way of doing this nicely and
safely. I hope to have that for 8.3.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2006-11-10 02:24:28 | Re: Frequent Update Project: Design Overview of HOT Updates |
Previous Message | Tom Lane | 2006-11-10 00:24:37 | Various breakages in new contrib/isn module |