From 686968314775d72a5c073ce9037d34bc60fe956d Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 23 Apr 2005 21:43:24 +0000 Subject: Remove item, not sure what it refers to: < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or < index using a sequential scan for highest/lowest values < < If only one value is needed, there is no need to sort the entire < table. Instead a sequential scan could get the matching value. < --- doc/src/FAQ/TODO.html | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 978e57a6267..e6daf796620 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Sat Apr 23 17:41:00 EDT 2005 +Last updated: Sat Apr 23 17:43:18 EDT 2005

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -782,11 +782,6 @@ first.

Add missing optimizer selectivities for date, r-tree, etc -
Allow ORDER BY ... LIMIT 1 to select high/low value without sort or - index using a sequential scan for highest/lowest values -
If only one value is needed, there is no need to sort the entire - table. Instead a sequential scan could get the matching value. -
Precompile SQL functions to avoid overhead
Create utility to compute accurate random_page_cost value
Improve ability to display optimizer analysis using OPTIMIZER_DEBUG -- cgit v1.2.3