Re: Lazy JIT IR code generation to increase JIT speed with partitions

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Luc Vlaming <luc(at)swarm64(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lazy JIT IR code generation to increase JIT speed with partitions
Date: 2022-06-27 15:37:39
Message-ID: 20220627153739.u7sb5i4kse2tgnjp@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2021-Jan-18, Luc Vlaming wrote:

> I would like this topic to somehow progress and was wondering what other
> benchmarks / tests would be needed to have some progress? I've so far
> provided benchmarks for small(ish) queries and some tpch numbers, assuming
> those would be enough.

Hi, some time ago I reported a case[1] where our JIT implementation does
a very poor job and perhaps the changes that you're making could explain
what is going on, and maybe even fix it:


The query for which I investigated the problem involved some pg_logical
metadata tables, so I didn't post it anywhere public; but the blog post
I found later contains a link to a query that shows the same symptoms,
and which is luckily still available online:
I attach it here in case it goes missing sometime.

Álvaro Herrera 48°01'N 7°57'E —

Attachment Content-Type Size
go_api_metadata_pg_query.sql application/sql 6.3 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Isaac Morland 2022-06-27 16:03:20 Re: Making the subquery alias optional in the FROM clause
Previous Message Julien Rouhaud 2022-06-27 15:34:13 Re: Emit postgres log messages that have security or PII with special flags/error code/elevel