| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Memoize in between of two JOIN nodes |
| Date: | 2025-03-07 01:13:27 |
| Message-ID: | CAMbWs4_qMy5ZGCRuSCEe9hB1r_G69neVLJPDtykN+t+umCOo6g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Mar 6, 2025 at 8:17 PM Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
> Playing with memoisation, I found the case where the Memoize is put over
> a JOIN node (see attachment).
> I recall a discussion we had with Richard in which he mentioned [1] that
> this feature is still not implemented and is hard to design.
> I'm not sure, but may it be a sign of a potential bug?
In your case, the Memoize node is added on top of a base relation of a
subquery RTE, not a join relation. The final plan might be kind of
confusing because the SubqueryScan node is considered trivial and is
removed from the plan tree.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Inokuchi | 2025-03-07 06:02:35 | Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately |
| Previous Message | Richard Guo | 2025-03-07 00:49:53 | Re: BUG #18832: Segfault in GrantLockLocal |