On Jan 23, 2019, at 6:46 AM, Tom Lane wrote:
>
> Oleksandr Shulgin writes:
>> On Wed, Jan 23, 2019 at 9:44 AM Donald Dong wrote:
>>> 1. Enumerate all the plans
>
>> So enumerating all possible plans stops being practical for even slightly
>> complicated queries.
>
> Yes. You can *not* disabl
Oleksandr Shulgin writes:
> On Wed, Jan 23, 2019 at 9:44 AM Donald Dong wrote:
>> 1. Enumerate all the plans
> So enumerating all possible plans stops being practical for even slightly
> complicated queries.
Yes. You can *not* disable the planner's aggressive pruning of losing
paths and subpat
On Wed, Jan 23, 2019 at 9:44 AM Donald Dong wrote:
>
> 1. Enumerate all the plans
>
Not sure this is going to work. Because of the total number of possible
plans is somewhere
around O(n!), if I'm not mistaken, in terms of number of joined relations
times the available
access methods times the p
Hi,
I'm working on an extension which analyzes all possible plans
generated by the planner. I believe this extension would become
useful for benchmarking the planner (e.g. the performance of the
estimation and the cost model) and better understanding the cases
where the planners would make a subop
