aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2006-01-20 16:42:02 +0000
committerBruce Momjian <bruce@momjian.us>2006-01-20 16:42:02 +0000
commit4a651c97055c700259965f6aa71da68440a48663 (patch)
tree61cb09e8bf9a532259c9f28744f89b59328a538b
parent517056bd08e6f0b12151d6ee68de56ca7aa2c36a (diff)
downloadpostgresql-4a651c97055c700259965f6aa71da68440a48663.tar.gz
postgresql-4a651c97055c700259965f6aa71da68440a48663.zip
Update EXPLAIN wording for GEQO usage.
-rw-r--r--doc/src/sgml/ref/explain.sgml10
1 files changed, 9 insertions, 1 deletions
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
-->
@@ -151,6 +151,14 @@ ROLLBACK;
</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
appears as a query result (formatted like a table with a single