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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
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)
Date: 2025-10-23 00:20:52
Message-ID: CAApHDvriMJeNnrPXae1JzDOc+u+efzivXBOVJ0OCRQca2shwuQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2025-10-23 00:29:19 Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
Previous Message Euler Taveira 2025-10-22 22:41:37 Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10