mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update EXPLAIN wording for GEQO usage.

Browse Source
This commit is contained in:
Bruce Momjian 2006-01-20 16:41:55 +00:00
parent 413d492d32
commit 138fdf32bb
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/ref/explain.sgml
View File

@ -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.36 2006/01/20 16:41:55 momjian Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -151,11 +151,13 @@ ROLLBACK;
</para> </para>
<para> <para>
Prior to <productname>PostgreSQL</productname> 7.3, the plan was Genetic query optimization (<acronym>GEQO</acronym>) randomly
emitted in the form of a <literal>NOTICE</literal> message. Now it tests execution plans. Therefore, when the number of tables exceeds
appears as a query result (formatted like a table with a single <varname>geqo_threshold</> causing genetic query optimization to be
text column). used, the execution plan is likely to change each time the statement
is executed.
</para> </para>
</refsect1> </refsect1>
<refsect1> <refsect1>