Re: An incorrect check in get_memoize_path
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-04-14T06:49:59Z
Lists: pgsql-hackers
Attachments
- v2-0001-Fix-an-incorrect-check-in-get_memoize_path.patch (application/octet-stream) patch v2-0001
On Mon, Apr 7, 2025 at 4:50 PM Richard Guo <guofenglinux@gmail.com> wrote: > Hence, I propose the attached patch for the fix. > > BTW, there is a XXX comment there saying that maybe we can make the > remaining join quals part of the inner scan's filter instead of the > join filter. I don't think this is possible in all cases. In the > above query, 'coalesce(t2.b) = t3.b' cannot be made part of t3's scan > filter, according to join_clause_is_movable_into. So I removed that > comment in the patch while we're here. > > Any thoughts? Here is an updated patch with a commit message. Regarding backporting, I'm inclined not to, given the lack of field reports. Any objections to pushing it? Thanks Richard
Commits
-
Fix an incorrect check in get_memoize_path
- 3b35f9a4c5e0 18.0 landed