| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, 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-03-13 18:29:20 |
| Message-ID: | 2827970.1741890560@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-13 18:31:24 | Re: Adding support for SSLKEYLOGFILE in the frontend |
| Previous Message | Jacob Champion | 2025-03-13 18:29:16 | Re: Adding support for SSLKEYLOGFILE in the frontend |