11<!--
2- $Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.50 2001/02/10 00:50:18 petere Exp $
2+ $Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.51 2001/02/15 04:28:50 tgl Exp $
33-->
44
55<Chapter Id="runtime">
@@ -639,7 +639,7 @@ env PGOPTIONS='-c geqo=off' psql
639639 algorithm: The pool size is the number of individuals in one
640640 population. Valid values are between 128 and 1024. If it is
641641 set to 0 (the default) a pool size of 2^(QS+1), where QS
642- is the number ofrelations in the query, is taken. The effort
642+ is the number ofFROM items in the query, is taken. The effort
643643 is used to calculate a default for generations. Valid values
644644 are between 1 and 80, 40 being the default. Generations
645645 specifies the number of iterations in the algorithm. The
@@ -659,9 +659,10 @@ env PGOPTIONS='-c geqo=off' psql
659659 <term>GEQO_THRESHOLD (<type>integer</type>)</term>
660660 <listitem>
661661 <para>
662- Only use genetic query optimization for queries with at least
663- this many relations involved. The default is 11. For less
664- relations it is probably more efficient to use the
662+ Use genetic query optimization to plan queries with at least
663+ this many FROM items involved. (Note that a JOIN construct
664+ counts as only one FROM item.) The default is 11. For simpler
665+ queries it is usually best to use the
665666 deterministic, exhaustive planner.
666667 </para>
667668 </listitem>