Tomas Vondra <[email protected]> writes: > On 12/2/25 17:05, Tomas Vondra wrote: >> So it was ~19h for a while (started at ~14h about 4y back). And then >> between September 14 and 22 it jumped to ~32h. Which seems like a lot.
> After bisecting this, it seems to have changed in this commit: > commit 1eccb93150707acfcc8f24556a15742a6313c8ac (HEAD -> stats-ext) > Author: Tom Lane <[email protected]> > Date: Sat Sep 20 12:44:52 2025 -0400 > Re-allow using statistics for bool-valued functions in WHERE. Ugh. > Attached is a perf-report for this, but the interesting part is: > --99.51%--plpgsql_exec_function Yeah, I can imagine that constantly flushing the cached plan for that plpgsql function would be bad. Let me see if I can reformulate that test without using a plpgsql function --- right offhand, it's not obvious why a built-in function wouldn't serve the purpose just as well. regards, tom lane
