Re: Consider low startup cost in add_partial_path - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Consider low startup cost in add_partial_path
Date
Msg-id CA+Tgmob57CDgacucdcDhW+=jNQnB6J4wx9b+WujKboDJM18wBw@mail.gmail.com
Whole thread
In response to Re: Consider low startup cost in add_partial_path  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: Consider low startup cost in add_partial_path
List pgsql-hackers
On Tue, Feb 17, 2026 at 2:44 AM Richard Guo <guofenglinux@gmail.com> wrote:
> Yeah, I agree that we should consider startup cost for partial paths,
> given that cost_gather (and cost_gather_merge) accounts for the
> subpath's startup_cost when calculating the cost of the Gather path.
>
> The changes LGTM.  I noticed one comment that may need to be updated
> accordingly:
>
>  *    As in add_path, the partial_pathlist is kept sorted with the cheapest
>  *    total path in front. ...
>
> This is not true anymore.  The partial_pathlist is now sorted by
> disabled_nodes and then by cheapest total cost.

Thanks. I have committed 0001 after adjusting that comment.

Here's the remaining patch once again. No comments on this one?

--
Robert Haas
EDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Hash aggregate collisions cause excessive spilling
Next
From: Robert Haas
Date:
Subject: Re: pg_plan_advice