Re: Redundant Result node
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-08-23T03:56:15Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid unnecessary post-sort projection
- 9626068f1333 18.0 landed
Richard Guo <guofenglinux@gmail.com> writes: > On Fri, Aug 23, 2024 at 11:19 AM Tom Lane <tgl@sss.pgh.pa.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