marcin mank <marcin(dot)mank(at)gmail(dot)com> writes:
> This is pretty off-topic, but if we had some upper bound on the cost
> of the complete plan, we could discard pieces of the plan that already
> cost more.
> One way to get the upper bound is to generate the plan in depth-first
> fashion, instead of the current breadth-first. Instead of bottom-up
> dynamic programming, employ memoization.
Well, the breadth-first approach also allows elimination of large parts
of the search space. It's not immediately obvious to me that the above
would be better. You should be able to try it if you want though ---
these days, there's even a hook to allow replacement of the join search
strategy at runtime.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Jeff Davis||Date: 2009-11-28 03:18:20|
|Subject: Re: operator exclusion constraints|
|Previous:||From: Greg Smith||Date: 2009-11-28 01:28:13|
|Subject: Re: [PATCH 4/4] Add tests to dblink covering use of COPY
pgsql-committers by date
|Next:||From: Bruce Momjian||Date: 2009-11-28 15:04:55|
|Subject: pgsql: test_fsync: Improve test descriptions displayed during |
|Previous:||From: Tom Lane||Date: 2009-11-28 01:23:08|
|Subject: Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a |