Re: Performance issues with v18 SQL-language-function changes
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, Alexander Pyhalov <a.pyhalov@postgrespro.ru>,
Pavel Stehule <pavel.stehule@gmail.com>
Date: 2025-04-14T14:38:29Z
Lists: pgsql-hackers
On Sun, Apr 13, 2025 at 3:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > create function fx(p_summa bigint) returns text immutable strict > return ltrim(to_char(p_summa, '999 999 999 999 999 999 999 999')); > > explain analyze select fx(i) from generate_series(1,1000000) as i(i); > > you arrive at the rude discovery that 0dca5d68d is about 50% slower > than 0dca5d68d^, because the old implementation builds a plan for fx() > only once and then re-uses it throughout the query. I agree that we should do something about this. I haven't reviewed your patches but the approach sounds broadly reasonable. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
Don't use a tuplestore if we don't have to for SQL-language functions.
- e83a8ae44729 18.0 landed
-
Change SQL-language functions to use the plan cache.
- 0dca5d68d7be 18.0 cited
-
contrib/pageinspect: Use SQL-standard function bodies.
- 68ff25eef125 18.0 cited