Re: bug: query returns different result with and without memoization.

From: "Yilin Zhang" <jiezhilove(at)126(dot)com>
To: "Richard Guo" <guofenglinux(at)gmail(dot)com>
Cc: "David Rowley" <dgrowleyml(at)gmail(dot)com>, "Jacob Brazeal" <jacob(dot)brazeal(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: bug: query returns different result with and without memoization.
Date: 2026-10-30 06:03:00
Message-ID: 1de3280d.400a.1a18b678718.Coremail.jiezhilove@126.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2026-10-28 10:23:43, "Richard Guo" <guofenglinux(at)gmail(dot)com> wrote:
>Good point. I agree that we should not give up Memoize only because a
>buried Param is not hashable. For such a Param, purging the cache
>whenever it changes is enough to get correct results.
>...
>I plan to push them (or at least 0001, back-patched to 14) in a few
>days if there are no objections, since the next minor release is just

>around the corner.

Hi,
Thank you for working on this bug.
Yes, the code in v3 is simpler and more effective.
LGTM.

Best regards,
Yilin Zhang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message solai v 2026-10-30 06:46:45 Re: Enable partitionwise join for partition keys wrapped by RelabelType
Previous Message Kirill Reshke 2026-10-30 05:44:00 Re: [PG19] pg_upgrade --check passes, then the upgrade fails