From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 20 Jan 2006 16:42:02 +0000 (+0000)
Subject: Update EXPLAIN wording for GEQO usage.
X-Git-Tag: REL8_1_3~35
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4a651c97055c700259965f6aa71da68440a48663;p=thirdparty%2Fpostgresql.git

Update EXPLAIN wording for GEQO usage.
---

diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml
index 748e7e16ae2..dd1f07b40df 100644
--- a/doc/src/sgml/ref/explain.sgml
+++ b/doc/src/sgml/ref/explain.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/explain.sgml,v 1.35 2005/01/04 00:39:53 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/explain.sgml,v 1.35.6.1 2006/01/20 16:42:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -150,6 +150,14 @@ ROLLBACK;
    the query, and consequently an inferior query plan may be chosen.
   </para>
 
+  <para>
+   Genetic query optimization (<acronym>GEQO</acronym>) randomly 
+   tests execution plans.  Therefore, when the number of tables exceeds
+   <varname>geqo_threshold</> causing genetic query optimization to be 
+   used, the execution plan is likely to change each time the statement
+   is executed.
+  </para>
+
   <para>
    Prior to <productname>PostgreSQL</productname> 7.3, the plan was
    emitted in the form of a <literal>NOTICE</literal> message.  Now it