| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> | 
|---|---|
| To: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> | 
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> | 
| Subject: | Re: SQLFunctionCache and generic plans | 
| Date: | 2025-02-26 19:34:42 | 
| Message-ID: | CAFj8pRD-JcaGCktoWqGTt7TEb1zgENajVQwuhbHFfSMRH7+XPw@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
hI
I can confirm 60% speedup for execution of function fx and fx3 - both
functions are very primitive, so for real code the benefit can be higher
Unfortunately, there is about 5% slowdown for inlined code, and for just
plpgsql code too.
I tested fx4
create or replace function fx4(int) returns int immutable as $$ begin
return $1 + $1; end $$ language plpgsql;
and fx2
create or replace function fx2(int) returns int as $$ select 2 * $1; $$
language sql immutable;
and execution of patched code is about 5% slower. It is strange so this
patch has a negative impact on plpgsql execution.
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-02-26 19:36:04 | Re: Anti join confusion | 
| Previous Message | Nikolay Shaplov | 2025-02-26 19:33:58 | Re: [PATCH] New [relation] option engine |