Re: PG 11 JIT deform failure

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,didier <did447(at)gmail(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 11 JIT deform failure
Date: 2019-06-13 18:35:32
Message-ID: 0BECEC12-5E7B-464B-80C5-B5938C3EA76C@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On June 13, 2019 11:08:15 AM PDT, didier <did447(at)gmail(dot)com> wrote:
>Extensions can do it, timescaledb in this case with:
>INSERT INTO ... RETURNING *;
>
>Or replacing the test in llvm_compile_expr with an Assert in
>slot_compile_deform ?

In that case we ought to never generate a deform expression step - core code doesn't afair. That's only done I'd there's actually something to deform. I'm fine with adding an assert tough

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-06-13 19:53:46 Re: Custom table AMs need to include heapam.h because of BulkInsertState
Previous Message didier 2019-06-13 18:08:15 Re: PG 11 JIT deform failure