Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters) - Mailing list pgsql-hackers

From Benedikt Grundmann
Subject Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)
Date
Msg-id CADbMkNMXG83KHEpv=ZLBgHf4CqsLWp=ODEMC-Hw3G6cBH2O2SQ@mail.gmail.com
Whole thread Raw
In response to More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)
List pgsql-hackers
On Wed, Dec 30, 2015 at 7:16 AM, David Rowley <david.rowley@2ndquadrant.com> wrote:

A number of ideas were suggested on the other thread about how we might go about solving this problem. In [3] Simon talked about perhaps enabling extra optimisations when the planner sees that the plan will cost more than some given threshold. That's perhaps an option, but may not work well for optimisations which must take place very early in planning, for example [4].

A small tweak on 3 to deal with 4.  If the returned plan cost is quite high (say you estimate minutes+) you could just restart planning from scratch with all costly planning enabled, because even in the worst case (that is the additional options don't find a better plan), the total planning cost won't matter much in the grand scheme of things.
 

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Refactoring of LWLock tranches
Next
From: "Shulgin, Oleksandr"
Date:
Subject: Re: custom function for converting human readable sizes to bytes