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

From: 纪晓曦 <sheepjxx(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Postgres General Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Where can I get the number of plans that considered by Planner?
Date: 2009-10-13 02:19:36
Message-ID: 37a11ce00910121919x2669aa04vb368fdbcb6d49d50@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(at)sss(dot)pgh(dot)pa(dot)us>

> =?UTF-8?B?57qq5pmT5pum?= <sheepjxx(at)gmail(dot)com> 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
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2009-10-13 02:32:53 Re: Is there a way to know if trigger is invoked by the code from another trigger
Previous Message Dan Kortschak 2009-10-13 01:29:54 Re: `must be superuser to COPY to or from a file' - using perl DBI - approaches to work around this