| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Status of plperl inter-sp calling |
| Date: | 2010-01-05 21:05:40 |
| Message-ID: | 3963A35D-C4A0-4BF8-8E6F-EF5FABCF0276@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 5, 2010, at 12:59 PM, Tim Bunce wrote:
> So you're suggesting SP::foo(...) _always_ executes foo(...) via bunch
> of spi_* calls. Umm. I thought performance was a major driving factor.
> Sounds like you're more keen on syntactic sugar.
I'm saying do both. Make the cached version the one that will be used most often, but make available a second version that doesn't cache so that you get the sugar and the polymorphic dispatch. Such would only have to be used in cases where there is more than one function that takes the same number of arguments. The rest of the time -- most of the time, that is -- one can use the cached version.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2010-01-05 21:08:58 | Re: true serializability and predicate locking |
| Previous Message | Bruce Momjian | 2010-01-05 21:00:11 | Re: pg_migrator issues |