In our first JIT episode , we discussed how we could, using copy-patch, easily create a JIT compiler for PostgreSQL, with a slight improvement in performance compared to the PostgreSQL interpreter.
Visit pinaraf.info → RSS feedOn Hacker News Mar 2024 – Oct 2025
Software Engineering 2Systems & Performance 1Databases & Data 1
Sometimes, I don’t know why I do things. It’s one of these times. A few months ago, Python 3.13 got its JIT engine, built with a new JIT compiler construction methodology (copy-patch, cf. research paper ). After reading the paper, I was sold and I just had to try it with PostgreSQL. And what a fun ride it’s been so…
Since my previous blog entry about JIT compiler for PostgreSQL, sadly not much happened due to a lack of time, but still some things were done (biggest improvement was the port to ARM64, a few optimizations, implementing more opcodes…). But I am often asking myself how to really beat the interpreter… And on “modern”…