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 603c8f070912301617j6a587cb8g313a23164d440d41@mail.gmail.com
Whole thread Raw
In response to Status of plperl inter-sp calling  (Tim Bunce <Tim.Bunce@pobox.com>)
Responses Re: Status of plperl inter-sp calling  ("David E. Wheeler" <david@kineticode.com>)
Re: Status of plperl inter-sp calling  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-hackers
On Wed, Dec 30, 2009 at 5:54 PM, Tim Bunce <Tim.Bunce@pobox.com> 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.?

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Hot Standy introduced problem with query cancel behavior
Next
From: "David E. Wheeler"
Date:
Subject: Re: Status of plperl inter-sp calling