From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Status of plperl inter-sp calling |
Date: | 2009-12-31 00:41:42 |
Message-ID: | 3E7F47EA-6F5F-4BD7-9A29-026A8FDEEFAD@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Dec 30, 2009, at 4:17 PM, Robert Haas wrote:
>> That much works currently. Behind the scenes, when a stored procedure is
>> loaded into plperl the code ref for the perl sub is stored in a cache.
>> Effectively just
>> $cache{$name}[$nargs] = $coderef;
>
> That doesn't seem like enough to guarantee that you've got the right
> function. What if you have two functions with the same number of
> arguments but different argument types? And what about optional
> arguments, variable arguments, etc.?
As Tim said elsewhere:
> I don't see either of those as significant issues: "If you need more
> control for a particular SP then don't use SP::* to call that SP."
Best,
Davdi
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-12-31 01:40:09 | Re: Thoughts on statistics for continuously advancing columns |
Previous Message | Robert Haas | 2009-12-31 00:17:44 | Re: Status of plperl inter-sp calling |