| From: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, 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:31:23 |
| Message-ID: | 20100105213123.GJ2505@timac.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 05, 2010 at 01:05:40PM -0800, David E. Wheeler wrote:
> 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.
I think I have a best-of-both solution. E-mail to follow...
Tim.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-05 21:45:18 | Re: Stats for inheritance trees |
| Previous Message | Kevin Grittner | 2010-01-05 21:24:39 | Re: true serializability and predicate locking |