aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-06-16 00:09:12 +0000
committerBruce Momjian <bruce@momjian.us>2002-06-16 00:09:12 +0000
commit0dbfea39f313fbd24a1754a701a85815229fe262 (patch)
tree8cd4ee381d1e1f4d39b32dfd396a29957903da90 /doc/src
parentb50cbbd66b8835682982d553b348d017a850f76a (diff)
downloadpostgresql-0dbfea39f313fbd24a1754a701a85815229fe262.tar.gz
postgresql-0dbfea39f313fbd24a1754a701a85815229fe262.zip
Remove KSQO from GUC and move file to _deadcode.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/runtime.sgml30
1 files changed, 1 insertions, 29 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 057a45b856a..1a26e9d7942 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.118 2002/06/15 19:58:53 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.119 2002/06/16 00:09:11 momjian Exp $
-->
<Chapter Id="runtime">
@@ -760,34 +760,6 @@ env PGOPTIONS='-c geqo=off' psql
</varlistentry>
<varlistentry>
- <term><varname>KSQO</varname> (<type>boolean</type>)</term>
- <listitem>
- <para>
- The <firstterm>Key Set Query Optimizer</firstterm>
- (<acronym>KSQO</acronym>) causes the query planner to convert
- queries whose <literal>WHERE</> clause contains many OR'ed AND
- clauses (such as <literal>WHERE (a=1 AND b=2) OR (a=2 AND b=3)
- ...</literal>) into a union query. This method can be faster
- than the default implementation, but it doesn't necessarily give
- exactly the same results, since <literal>UNION</> implicitly
- adds a <literal>SELECT DISTINCT</> clause to eliminate identical
- output rows. <acronym>KSQO</acronym> is commonly used when
- working with products like <productname>Microsoft
- Access</productname>, which tend to generate queries of this
- form.
- </para>
-
- <para>
- The <acronym>KSQO</acronym> algorithm used to be absolutely
- essential for queries with many OR'ed AND clauses, but in
- <productname>PostgreSQL</productname> 7.0 and later the standard
- planner handles these queries fairly successfully; hence the
- default is off.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><varname>RANDOM_PAGE_COST</varname> (<type>floating point</type>)</term>
<listitem>
<para>