[HACKERS] Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)

On Wed, Dec 30, 2015 at 08:16:28PM +1300, David Rowley wrote: > On [1] I suggested an idea to make improvements to the planner around the > Equivalence Class code. Later in [2] Tom raised concerns with this adding > too many planning cycles for a perhaps not common enough situation. I > don't

[HACKERS] Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)

On 12/30/2015 10:30 PM, David Rowley wrote: On 31 December 2015 at 01:24, Tomas Vondra > wrote: Personally I'd like to see automatic plan caching occur in PostgreSQL. There is a bit of a problem with it in regards to a query

[HACKERS] Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)

On 31 December 2015 at 01:24, Tomas Vondra wrote: > On 12/30/2015 08:16 AM, David Rowley wrote: > >> >> I do strongly believe that we need to come up with something to >> solve this problem. I already summarised my thoughts on the other >> thread. >> > > One

[HACKERS] Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)

On 31 December 2015 at 04:39, Evgeniy Shishkin wrote: > > > On 30 Dec 2015, at 10:16, David Rowley > wrote: > > > > A number of ideas were suggested on the other thread about how we might > go about solving this problem. In [3] Simon talked

[HACKERS] Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)

On 12/30/2015 08:16 AM, David Rowley wrote: I do strongly believe that we need to come up with something to solve this problem. I already summarised my thoughts on the other thread. One approach that I don't see mentioned on any of the threads is plan caching, which allows reusing the plan