Comment 2 for bug 2042158

Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

I've also run into this issue on Postgres 14, and the recommendation in Blake's branch (setting jit_above_cost = -1 in postgresql.conf) resolved the problem for me.