From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 11 Oct 2001 21:16:26 +0000 (+0000)
Subject: Document use of GEQO param in subquery pullups.
X-Git-Tag: REL7_2_BETA1~135
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e98476eb032bd4dc32ca97212b660cad0bbadef4;p=postgresql

Document use of GEQO param in subquery pullups.
---

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index b3d68e4006..0bb3eb1c44 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.89 2001/10/09 18:46:00 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.90 2001/10/11 21:16:26 momjian Exp $
 -->
 
 <Chapter Id="runtime">
@@ -719,7 +719,9 @@ env PGOPTIONS='-c geqo=off' psql
         this many FROM items involved.  (Note that a JOIN construct
 	counts as only one FROM item.) The default is 11. For simpler
 	queries it is usually best to use the
-        deterministic, exhaustive planner.
+        deterministic, exhaustive planner.  This parameter also controls
+        how hard the optimizer will try to merge subquery
+        <literal>FROM</literal> clauses into the upper query.
        </para>
       </listitem>
      </varlistentry>