Re: Status of plperl inter-sp calling - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Status of plperl inter-sp calling
Date
Msg-id 603c8f070912311014h45589375uf451362b5d40606f@mail.gmail.com
Whole thread Raw
In response to Re: Status of plperl inter-sp calling  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Status of plperl inter-sp calling  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-hackers
On Wed, Dec 30, 2009 at 7:41 PM, David E. Wheeler <david@kineticode.com> wrote:
> 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."

Sorry, I missed that.  I guess it seems weird to me to handle
overloading, but only partially.  If we're OK with punting, why not
punt the whole thing and just have $cache{$name} = $coderef?

...Robert


pgsql-hackers by date:

Previous
From: "Turner, Ian"
Date:
Subject: Re: Re-enabling SET ROLE in security definer functions
Next
From: "Kevin Grittner"
Date:
Subject: Re: Serializable Isolation without blocking