File tree Expand file tree Collapse file tree 2 files changed +2
-13
lines changed Expand file tree Collapse file tree 2 files changed +2
-13
lines changed Original file line number Diff line number Diff line change 22PostgreSQL TODO List
33====================
44Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
5- Last updated: Sat Apr 23 17:41:00 EDT 2005
5+ Last updated: Sat Apr 23 17:43:18 EDT 2005
66
77The most recent version of this document can be viewed at
88http://www.postgresql.org/docs/faqs.TODO.html.
@@ -858,12 +858,6 @@ Optimizer / Executor
858858====================
859859
860860* Add missing optimizer selectivities for date, r-tree, etc
861- * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or
862- index using a sequential scan for highest/lowest values
863-
864- If only one value is needed, there is no need to sort the entire
865- table. Instead a sequential scan could get the matching value.
866-
867861* Precompile SQL functions to avoid overhead
868862* Create utility to compute accurate random_page_cost value
869863* Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Original file line number Diff line number Diff line change 88< body bgcolor ="#FFFFFF " text ="#000000 " link ="#FF0000 " vlink ="#A00000 " alink ="#0000FF ">
99< h1 > < a name ="section_1 "> PostgreSQL TODO List</ a > </ h1 >
1010< p > Current maintainer: Bruce Momjian (< a href ="mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ a > )< br />
11- Last updated: Sat Apr 23 17:41:00 EDT 2005
11+ Last updated: Sat Apr 23 17:43:18 EDT 2005
1212</ p >
1313< p > The most recent version of this document can be viewed at< br />
1414< a href ="http://www.postgresql.org/docs/faqs.TODO.html "> http://www.postgresql.org/docs/faqs.TODO.html</ a > .
@@ -782,11 +782,6 @@ <h1><a name="section_18">Optimizer / Executor</a></h1>
782782
783783< ul >
784784 < li > Add missing optimizer selectivities for date, r-tree, etc
785- </ li > < li > Allow ORDER BY ... LIMIT 1 to select high/low value without sort or
786- index using a sequential scan for highest/lowest values
787- < p > If only one value is needed, there is no need to sort the entire
788- table. Instead a sequential scan could get the matching value.
789- </ p >
790785 </ li > < li > Precompile SQL functions to avoid overhead
791786 </ li > < li > Create utility to compute accurate random_page_cost value
792787 </ li > < li > Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
You can’t perform that action at this time.
0 commit comments