PostgreSQL Begins Adding LLVM JIT Support For Faster Performance

Re:PostgreSQL Begins Adding LLVM JIT Support For Faster Perf... by tejasmanohar on Saturday April 07, 2018 @06:29PM (#16783387)

  There's not yet any caching around JITed programs,
  which makes it completely unsuitable for OLTP.

Oh, I see. Thanks for clarifying! You mentioned it was merged. Does this mean it'll land in stable soon? Will it be behind a flag, or does the planner just know when to use it?

  I can't imagine them doing that.

RE: Redshift, That's very unfortunate :|. I suppose that's another downside of AWS forking vs. say Citus who moved to the extension model. Though, this would really be perfect for Redshift's use cases... so I guess we'll see.

This is a step in the right direction regardless, but I'm curious how many people are specifically using pure Postgres for large-scale OLAP models (not including occasionally running one-off queries on their OLTP data).

[ Parent | on HN ]

Re:PostgreSQL Begins Adding LLVM JIT Support For Faster Perf... by anarazel on Saturday April 07, 2018 @06:35PM (#16783421)

> Oh, I see. Thanks for clarifying! You mentioned it was merged. Does this mean it'll land in stable soon?

It has been merged into the master branch, which'll become PostgreSQL 11. First beta will be in a few weeks. Release is planned to be in September (early I'd hope).

> Will it be behind a flag, or does the planner just know when to use it?

There's cost based logic that chooses it, yes. See https://www.postgresql.org/docs/devel/static/jit-decision.ht...

You can change those if you want to force JIT on/off.

[ Parent | on HN ]