From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Redundant Result node |
Date: | 2024-08-23 03:56:15 |
Message-ID: | 2127813.1724385375@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> On Fri, Aug 23, 2024 at 11:19 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm not sure you're considering "efficiency" in the right light.
> I agree that it’s always desirable to postpone work from path-creation
> time to plan-creation time. In this case, however, it’s a little
> different. The projection step could actually be avoided from the
> start if we perform the correct check in create_ordered_paths.
Well, the question is how expensive is the "correct check" compared
to what we're doing now. It might be cheaper than creating an extra
level of path node, or it might not. An important factor here is
that we'd pay the extra cost of a more complex check every time,
whether it avoids creation of an extra path node or not.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | shveta malik | 2024-08-23 05:08:51 | Re: Conflict Detection and Resolution |
Previous Message | Richard Guo | 2024-08-23 03:48:37 | Re: Redundant Result node |