Search Postgresql Archives

Re: Where can I get the number of plans that considered by Planner?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yeah, the problem is when I test large join, the plan considered by geqo is large than path. (3000+ vs 500+). However, the time used in optimizer of geqo is 1/4 of path. By the way, I use the same query.
Another thing is for the join of 2 tables, geqo consider 60-90 plans. 
In general, I think for large join, geqo consider less plans than path,  am I right?

2009/10/13 Tom Lane <tgl@xxxxxxxxxxxxx>
=?UTF-8?B?57qq5pmT5pum?= <sheepjxx@xxxxxxxxx> writes:
> Is it a reasonable idea to add a counter to set_cheapest?

You can try it but I think you'll find it's not terribly useful.
That will effectively just give you a count of the number of join
combinations that were considered (plus the number of base relations).

                       regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux