| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Time to drop old-style (V0) functions? |
| Date: | 2016-12-20 09:14:10 |
| Message-ID: | 20161220091410.ks37gwvupr7bb36o@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-12-20 09:59:43 +0100, Pavel Stehule wrote:
> In this case some benchmark can be very important (and interesting). I am
> not sure if faster function execution has significant benefit on Vulcano
> like executor.
It's fairly to see function calls as significant overhead. In fact, I
moved things *away* from a pure Vulcano style executor, and the benefits
weren't huge, primarily due to expression evaluation overhead (of which
function call overhead is one part). After JITing of expressions, it
becomes even more noticeable, because the overhead of the expression
evaluation is reduced.
I don't quite see why a Vulcano style executor should make function call
overhead meaningless?
Regards,
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-12-20 09:28:13 | Re: Time to drop old-style (V0) functions? |
| Previous Message | Beena Emerson | 2016-12-20 09:08:57 | Re: increasing the default WAL segment size |