pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vlad Arkhipov <arhipov@dc.baikal.ru>
To: pgsql-performance@postgresql.org
Subject: join/from_collapse_limit and geqo_threshold default values
Date: Fri, 23 May 2008 18:01:16 +0900
Message-ID: <483687DC.5030300@dc.baikal.ru> (raw)

I wonder why join_collapse_limit default values is set to 8 but 
geqo_threshold is 12. Optimizer doesn't change the order of JOIN's of 
queries that contains from 8 to 11 tables. Why it's 'wise' decision as 
documentation says?

from_collapse_limit (integer)

    The planner will merge sub-queries into upper queries if the
    resulting FROM list would have no more than this many items. Smaller
    values reduce planning time but might yield inferior query plans.
    The default is eight. It is usually wise to keep this less than
    geqo_threshold
    <http://www.postgresql.org/docs/8.3/static/runtime-config-query.html#GUC-GEQO-THRESHOLD;.
    For more information see Section 14.3
    <http://www.postgresql.org/docs/8.3/static/explicit-joins.html;.

Message-ID: <483687DC.5030300@dc.baikal.ru>
Permalink:  ../483687DC.5030300@dc.baikal.ru/
Also on:    postgresql.org/message-id/483687DC.5030300@dc.baikal.ru

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: arhipov@dc.baikal.ru
  Subject: Re: join/from_collapse_limit and geqo_threshold default values
  In-Reply-To: <483687DC.5030300@dc.baikal.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox