| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
| Cc: | Greg Sabino Mullane <greg(at)endpoint(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl |
| Date: | 2010-02-17 18:30:03 |
| Message-ID: | 6A9D0490-1179-46B3-9CB3-D002F6A857F4@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 17, 2010, at 4:28 AM, Tim Bunce wrote:
>> Yes, but if it's a variadic function, I suspect that it won't often be
>> called with the same number of args. So you'd potentially end up
>> caching a lot of extra stuff that would never be used again.
>
> Potentially. Patches welcome!
GitHub. ;-P
> Umm, perhaps F->funcname(@args), or PG->funcname(@args), or ... ?
>
> Anyone got any better suggestions?
PG is good. Or maybe DB?
>> By the way, I think it needs some documentation explaining how to load it inside PL/Perl.
>
> I thought about that, and started to write it, but dropped it for now.
> I'll wait till my "cunning plan" to share code with the Safe compartment
> (aka PostgreSQL::PLPerl::Injector) is done then document how call() can
> be used in both plperlu and plperl.
Ah, okay.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-17 18:47:40 | default parameters |
| Previous Message | Greg Sabino Mullane | 2010-02-17 18:04:14 | Re: [HACKERS] Listen/Notify payload and interfaces |