Re: [HACKERS] Optimizer speed and GEQO (was: nested loops in joins) - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] Optimizer speed and GEQO (was: nested loops in joins)
Date
Msg-id 36BC4FF4.C7A63095@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] Optimizer speed and GEQO (was: nested loops in joins)  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Optimizer speed and GEQO (was: nested loops in joins)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Why are we maintaining this huge Path List for every RelOptInfo
> structure if we only need the cheapest?  Why not store only the 
> cheapest plan, instead of generating all unique plans, then using only 
> the cheapest?

Just guessing here: does it use this same list to determine if a new
plan is a duplicate of a previously generated plan? Of course, maybe
that is not important, since any *cheaper* plan should be different from
any existing plan, and any plan of the same cost or higher could be
rejected.

Perhaps having the entire list of plans available makes it easier to
debug, especially when the stuff was in lisp (since in that environment
it is easy to traverse and manipulate these lists interactively)...
                      - Tom


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Optimizer speed and GEQO (was: nested loops in joins)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Optimizer speed and GEQO (was: nested loops in joins)