Horton

Re: SQLFunctionCache and generic plans

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Alexander Pyhalov <a.pyhalov@postgrespro.ru>, Alexander Korotkov <aekorotkov@gmail.com>, pgsql-hackers@lists.postgresql.org, Ronan Dunklau <ronan.dunklau@aiven.io>
Date: 2025-03-13T18:29:20Z
Lists: pgsql-hackers 
Pavel Stehule <pavel.stehule@gmail.com> writes:
> Maybe interesting change is the change of error message context

>  QUERY:   SELECT public.dep_req2() || ' req3b'.
> -CONTEXT:  SQL function "dep_req3b" during startup
> +CONTEXT:  SQL function "dep_req3b" statement 1

I'm not hugely excited about that given that it's just happening in
one case.  It might be useful to understand exactly why it's changing,
but I doubt it's something we need to "fix".

			regards, tom lane

Commits

  1. Fix performance issue in deadlock-parallel isolation test.

  2. functions.c: copy trees from source_list before parse analysis etc.

  3. Fix oversight in commit 0dca5d68d.

  4. Change SQL-language functions to use the plan cache.

  5. Reordering DISTINCT keys to match input path's pathkeys