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 trollied on Friday February 09, 2024 @03:49AM (#39312798)
Most optimisers cache the execution plan based on a hash of the query, hence reuse when using prepared statements vs not.

Oracle has an option to detect literals (CURSOR_SHARING) and essentially replace them with binds internally, in order to increase performance and stop the query pool getting filled up with the same statement(s).

[ Parent | on HN ]
Re:What's new in the Postgres 16 query planner (a.k.a. optim... by davidrowley on Friday February 09, 2024 @04:26AM (#39313059)
Postgres does not currently reuse JIT-compiled code. JIT will run each execution of the query. This may change in the next few years, likely starting with tuple deforming, as that's fairly reusable, per table for any query.
[ Parent | on HN ]