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

Re: Status of plperl inter-sp calling

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Status of plperl inter-sp calling
Date: 2009-12-31 00:17:44
Message-ID: 603c8f070912301617j6a587cb8g313a23164d440d41@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Dec 30, 2009 at 5:54 PM, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: David E. WheelerDate: 2009-12-31 00:41:42
Subject: Re: Status of plperl inter-sp calling
Previous:From: Robert HaasDate: 2009-12-31 00:09:57
Subject: Re: Hot Standy introduced problem with query cancel behavior

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