Re: add_partial_path() may remove dominated path but still in use - Mailing list pgsql-hackers

From Robert Haas
Subject Re: add_partial_path() may remove dominated path but still in use
Date
Msg-id CA+Tgmobc9X+ce_19E2+Bo3Pq++BtkP7Y3T-oHvx0Eom7R-UwxQ@mail.gmail.com
Whole thread Raw
In response to Re: add_partial_path() may remove dominated path but still in use  (Kohei KaiGai <kaigai@heterodb.com>)
Responses Re: add_partial_path() may remove dominated path but still in use  (Kohei KaiGai <kaigai@heterodb.com>)
List pgsql-hackers
On Wed, Jan 9, 2019 at 12:44 AM Kohei KaiGai <kaigai@heterodb.com> wrote:
> So, is it sufficient if set_rel_pathlist_hook is just relocated in
> front of the generate_gather_paths?
> If we have no use case for the second hook, here is little necessity
> to have the post_rel_pathlist_hook() here.
> (At least, PG-Strom will use the first hook only.)

+1.  That seems like the best way to be consistent with the principle
that we need to have all the partial paths before generating any
Gather paths.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Improve selectivity estimate for range queries
Next
From: Tom Lane
Date:
Subject: Re: NOTIFY and pg_notify performance when deduplicating notifications