Re: JIT: The nullness of casetest.value can be determined at the JIT compile time.

From: Xing Guo <higuoxing(at)gmail(dot)com>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: JIT: The nullness of casetest.value can be determined at the JIT compile time.
Date: 2024-09-03 15:18:39
Message-ID: CACpMh+AWarmG=aKy6KUyyWVTKLedBJzZMTQG3TKPN5EGVii9TA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 3, 2024 at 8:09 PM Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
>
> On 8/31/24 10:04 AM, Xing Guo wrote:
> > The nullness of casetest.value can be determined at the JIT compile
> > time. We can emit fewer codes by utilizing this property. The attached
> > patch is trying to fix it.
>
> I have not reviewed the code yet but the idea seems good.
>
> But I wonder if we shouldn't instead simplify the code a bit by
> specializing these steps when generating them instead of doing the work
> runtime/while generating machine code. Yes, I doubt the performance
> benefits matter but I personally think the code is cleaner before my
> patch than after it.

+1 to the idea.

> Long term it would be nice to get rid off
> caseValue_datum/domainValue_datum as mentioned by Andres[1] but that is
> a bigger job so think that either your patch or my patch would make
> sense to apply before that.

I think your patch makes more sense than mine! Thanks!

Best Regards,
Xing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-09-03 15:33:02 Re: Partitioned tables and [un]loggedness
Previous Message Robert Haas 2024-09-03 15:06:32 Re: scalability bottlenecks with (many) partitions (and more)