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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Xing Guo <higuoxing(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, 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: 2025-01-30 03:29:32
Message-ID: 3070951.1738207772@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> Huge +1 for cleaning up this abuse of caseValue_datum/domainValue_datum.
> While correct and sensible if we continue the abuse, these patches feel
> like putting lipstick on a pig.

Agreed. I spent some time trying to do it better, with results
shown at [1]. If we adopt that idea, then the executor's support
for CaseTestExpr will go away, so there's little point in pursuing
that half of the patch given here. However, I concluded that there's
insufficient reason to redesign CoerceToDomainValue, so we could
still push forward with that half of this patch.

regards, tom lane

[1] https://www.postgresql.org/message-id/3068812.1738206654@sss.pgh.pa.us

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2025-01-30 03:33:44 Re: Index AM API cleanup
Previous Message Tom Lane 2025-01-30 03:10:54 Getting rid of CaseTestExpr (well, partially)