Re: MergeAppend could consider sorting cheapest child path - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: MergeAppend could consider sorting cheapest child path
Date
Msg-id e1d3f1b5-a541-4097-85e0-50055c937d28@gmail.com
Whole thread Raw
In response to Re: MergeAppend could consider sorting cheapest child path  (Alexander Pyhalov <a.pyhalov@postgrespro.ru>)
Responses Re: MergeAppend could consider sorting cheapest child path
List pgsql-hackers
On 5/5/2025 15:56, Alexander Pyhalov wrote:
> Andrei Lepikhov писал(а) 2025-05-05 14:38:
> Also logic a bit differs if path is NULL. In 
> get_cheapest_path_for_pathkeys_ext() we explicitly check for path being 
> NULL, in get_cheapest_fractional_path_for_pathkeys_ext() only after 
> calculating sort cost.
> 
> I've tried to fix comments a bit and unified functions definitions.
Generally seems ok, I'm not a native speaker to judge the comments. But:
if (base_path && path != base_path)

What is the case in your mind where the base_path pointer still may be 
null at that point?

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Fix slot synchronization with two_phase decoding enabled
Next
From: Jack Ng
Date:
Subject: RE: Changing shared_buffers without restart