From 0dbfea39f313fbd24a1754a701a85815229fe262 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sun, 16 Jun 2002 00:09:12 +0000 Subject: Remove KSQO from GUC and move file to _deadcode. --- doc/src/sgml/runtime.sgml | 30 +----------------------------- 1 file changed, 1 insertion(+), 29 deletions(-) (limited to 'doc/src') 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 @@ @@ -759,34 +759,6 @@ env PGOPTIONS='-c geqo=off' psql - - KSQO (boolean) - - - The Key Set Query Optimizer - (KSQO) causes the query planner to convert - queries whose WHERE clause contains many OR'ed AND - clauses (such as WHERE (a=1 AND b=2) OR (a=2 AND b=3) - ...) into a union query. This method can be faster - than the default implementation, but it doesn't necessarily give - exactly the same results, since UNION implicitly - adds a SELECT DISTINCT clause to eliminate identical - output rows. KSQO is commonly used when - working with products like Microsoft - Access, which tend to generate queries of this - form. - - - - The KSQO algorithm used to be absolutely - essential for queries with many OR'ed AND clauses, but in - PostgreSQL 7.0 and later the standard - planner handles these queries fairly successfully; hence the - default is off. - - - - RANDOM_PAGE_COST (floating point) -- cgit v1.2.3