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

Re: Status of plperl inter-sp calling

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: (view raw, whole thread or download thread mbox)
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."



In response to


pgsql-hackers by date

Next:From: Greg SmithDate: 2009-12-31 01:40:09
Subject: Re: Thoughts on statistics for continuously advancing columns
Previous:From: Robert HaasDate: 2009-12-31 00:17:44
Subject: Re: Status of plperl inter-sp calling

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