From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Ms swati chande <swativc(at)yahoo(dot)com> |
Subject: | Re: Using the GEQO |
Date: | 2009-07-16 09:29:15 |
Message-ID: | 200907161129.16019.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 16 July 2009 09:02:53 Ms swati chande wrote:
> 1. Since the value of geqo_threshold is12, does the geqo get automatically
> activated for queries with 12 or more joins?
No, not directly. It will get used for 12 joins with no predefined order.
This is a bit complicated by the fact that even a predefined order like:
a JOIN b ON (..) JOIN c ON (..) ...
might get reordered if the number of joins is less than join_collapse_limit.
See
http://www.postgresql.org/docs/current/static/explicit-joins.html
> 2. Can the geqo threshold be set to a smaller value like 4 or 5?
Yes
> 3. How do we come to know whether the geqo has been used to solve the query
> or not? Does Explain Analyze report it?
No, you cannot see it directly unless you recompile with different options.
> 4. If we change the value of geqo_threshold do we have to change any other
parameters necessarily?
No.
> Please let me know these basics on the use of the geqo.
Why do you want to specifically use GEQO? Just Research? Normally you try not
to get where GEQO is used ;-)
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Rafael Martinez | 2009-07-16 09:39:21 | Autovacuum and pg_stat_reset() |
Previous Message | Florian Weimer | 2009-07-16 09:28:45 | Working around spurious unique constraint errors due to SERIALIZABLE bug |