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

Re: Status of plperl inter-sp calling

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(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 18:14:39
Message-ID: 603c8f070912311014h45589375uf451362b5d40606f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Dec 30, 2009 at 7:41 PM, David E. Wheeler <david(at)kineticode(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2009-12-31 18:43:05
Subject: Re: Serializable Isolation without blocking
Previous:From: Turner, IanDate: 2009-12-31 18:09:40
Subject: Re: Re-enabling SET ROLE in security definer functions

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