Re: Add a greedy join search algorithm to handle large join problems

2025-12-02 Thread Chengpeng Yan
Hi, > On Dec 2, 2025, at 18:56, Tomas Vondra wrote: > > I think a much broader evaluation will be needed, comparing not just the > planning time, but also the quality of the final plan. Which for the > starjoin tests does not really matter, as the plans are all equal in > this regard. Many t

Re: Add a greedy join search algorithm to handle large join problems

2025-12-02 Thread Tomas Vondra
On 12/2/25 04:48, Chengpeng Yan wrote: > Hi hackers, > > This patch implements GOO (Greedy Operator Ordering), a greedy > join-order search method for large join problems, based on Fegaras (DEXA > ’98) [1]. The algorithm repeatedly selects, among all legal joins, the > join pair with the lowest es

Re: Add a greedy join search algorithm to handle large join problems

2025-12-02 Thread Chengpeng Yan
Hi, Thanks for taking a look. > On Dec 2, 2025, at 13:36, Dilip Kumar wrote: > > Is pgbench the right workload to test this, I mean what are we trying > to compare here the planning time taken by DP vs GEQO vs GOO or the > quality of the plans generated by different join ordering algorithms > o

Re: Add a greedy join search algorithm to handle large join problems

2025-12-01 Thread Dilip Kumar
On Tue, Dec 2, 2025 at 9:18 AM Chengpeng Yan wrote: > > Hi hackers, > > This patch implements GOO (Greedy Operator Ordering), a greedy > join-order search method for large join problems, based on Fegaras (DEXA > ’98) [1]. The algorithm repeatedly selects, among all legal joins, the > join pair wit

Add a greedy join search algorithm to handle large join problems

2025-12-01 Thread Chengpeng Yan
Hi hackers, This patch implements GOO (Greedy Operator Ordering), a greedy join-order search method for large join problems, based on Fegaras (DEXA ’98) [1]. The algorithm repeatedly selects, among all legal joins, the join pair with the lowest estimated total cost, merges them, and continues unti