News for hackers. Stuff that matters.

A comment on What's new in the Postgres 16 query planner (a.k.a. optimizer). Parent comment

Re:What's new in the Postgres 16 query planner (a.k.a. optim... by Sesse__ on Friday February 09, 2024 @09:56AM (#39315405)
FWIW, I've seen planning+query times triple with JIT on, with no partitioned tables involved. It just takes forever to JIT sometimes. (This was with Postgres 13 and 14, IIRC.)

Update: I checked some old IRC logs, and found a query that took 1476 ms without JIT and 8754 ms with JIT on. And that is execution time, not planning time!

[ Parent | on HN ]
Re:What's new in the Postgres 16 query planner (a.k.a. optim... by davidrowley on Friday February 09, 2024 @08:01PM (#39322410)
Was there an indication of the number of functions compiled? There is work ongoing in this area, so feedback on this topic is very welcome on the PostgreSQL mailing lists.
[ Parent | on HN ]
Re:What's new in the Postgres 16 query planner (a.k.a. optim... by Sesse__ on Saturday February 10, 2024 @03:30AM (#39324567)
Not that I can remember, no. I don't have the details anymore; I delegated it to others to report to -perform, and then they never did. :-)
[ Parent | on HN ]