From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "bruce(at)momjian(dot)us" <bruce(at)momjian(dot)us>, lepihov(at)gmail(dot)com |
Subject: | Re: plan shape work |
Date: | 2025-09-23 21:27:37 |
Message-ID: | 3200728.1758662857@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Sep 22, 2025 at 2:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> In the second place, we should not need to add two hundred lines
>> of new code to createplan.c to accomplish this. Why not simply
>> bms_difference the joinrel's relids from the union of the inputs'
>> relids?
> ... On the other hand, I'm not sure that I'm interpreting your remarks
> correctly. When you say "bms_difference the joinrel's relids from the
> union of the inputs' relids" maybe you're specifically talking about
> the handling of the RTE_JOIN relids, and I don't care very much how we
> account for those. So I guess I need some clarification here as to
> what your thinking is.
What I'm saying is that I'd be much happier with 0003 if it looked
about like the attached. We do not need a heap of mechanism
redundantly proving that the planner is getting these things right
(and potentially containing its own bugs).
> Note that my goal for
> this commitfest was to get 0001-0004 committed, partly because I
> wasn't too sure whether the later patches might need some adjustment.
Fair enough. I think we can reach agreement on that much pretty quickly.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
v8-0001-Ensure-that-all-joinrel-RTIs-are-discoverable-fro.patch | text/x-diff | 12.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2025-09-23 21:57:34 | Re: libcurl in libpq.pc |
Previous Message | Jacob Champion | 2025-09-23 21:15:28 | Re: libcurl in libpq.pc |