Re: ERROR: XX000: could not find memoization table entry (reproducible)

Hello,

that's great news! Thank you!

Maybe just a followup question: will the fix also be included in upcoming postgresql 17 minor releases? Seeing that it's not only PG18 that's affected.

Thank you again!

Emmanuel

[logo]
Emmanuel Touzery
Razvoj programske opreme
E: emmanuel(dot)touzery(at)plandela(dot)si
PLANDELA d.o.o.
Cesta Ljubljanske brigade 23a
1000 Ljubljana
www.plandela.si<https://www.plandela.si>

________________________________
From: David Rowley <dgrowleyml(at)gmail(dot)com>
Sent: Thursday, October 23, 2025 2:20 AM
To: Emmanuel Touzery <emmanuel(dot)touzery(at)plandela(dot)si>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: ERROR: XX000: could not find memoization table entry (reproducible)

On Thu, 23 Oct 2025 at 10:13, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> The patch for the 1-liner.

I've pushed the fix for this [1]. The only other instance I saw of
LLVMBuildZExt for TypeDatum is in llvmjit_expr.c for "case
EEOP_BOOL_NOT_STEP". I didn't adjust this as it wasn't clear to me
that it was a problem. I expect the value being zero extended there is
either a 0 or 1, so didn't want to risk touching that code if it isn't
broken.

Emmanuel,

You should be seeing it in the next minor releases due around
mid-November. In the meantime, I suggest turning off
jit_tuple_deforming.

Many thanks for reporting this and coming up with the steps and backup
to reproduce the issue.

David

[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=10945148eec689cc114fe872d623c3c7c4f546e6

To sporo?ilo in morebitne priloge so poslovna skrivnost in namenjene izklju?no naslovniku, ?e ni navedeno druga?e. Prosimo, da vsebino sporo?ila in prilog varujete v skladu z veljavno zakonodajo in pogodbenimi obveznostmi. ?e ste sporo?ilo prejeli pomotoma, vas prosimo, da takoj obvestite po?iljatelja, sporo?ilo in priloge pa nepovratno uni?ite.

This e-mail and any attachments contain confidential information and is intended solely for the addressee unless stated otherwise. Please uphold strict confidentiality of the content of this message and attachments in accordance with the law and contractual obligations. If you have received this e-mail by mistake, please immediately notify the sender and irreversibly destroy this message and attachments.