Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 61cf535

Browse files
committed
Re-add item with better description:
> * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > index using a sequential scan for highest/lowest values > > Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > all values to return the high/low value. Instead The idea is to do a > sequential scan to find the high/low value, thus avoiding the sort. >
1 parent c5b08d3 commit 61cf535

File tree

2 files changed

+15
-2
lines changed

2 files changed

+15
-2
lines changed

doc/TODO

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated: Sun Apr 24 21:42:27 EDT 2005
5+
Last updated: Mon Apr 25 09:03:30 EDT 2005
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -862,6 +862,13 @@ Optimizer / Executor
862862
====================
863863

864864
* Add missing optimizer selectivities for date, r-tree, etc
865+
* Allow ORDER BY ... LIMIT 1 to select high/low value without sort or
866+
index using a sequential scan for highest/lowest values
867+
868+
Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort
869+
all values to return the high/low value. Instead The idea is to do a
870+
sequential scan to find the high/low value, thus avoiding the sort.
871+
865872
* Precompile SQL functions to avoid overhead
866873
* Create utility to compute accurate random_page_cost value
867874
* Improve ability to display optimizer analysis using OPTIMIZER_DEBUG

doc/src/FAQ/TODO.html

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
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: Sun Apr 24 21:42:27 EDT 2005
11+
Last updated: Mon Apr 25 09:03:30 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>.
@@ -787,6 +787,12 @@ <h1><a name="section_18">Optimizer / Executor</a></h1>
787787

788788
<ul>
789789
<li>Add missing optimizer selectivities for date, r-tree, etc
790+
</li><li>Allow ORDER BY ... LIMIT 1 to select high/low value without sort or
791+
index using a sequential scan for highest/lowest values
792+
<p> Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort
793+
all values to return the high/low value. Instead The idea is to do a
794+
sequential scan to find the high/low value, thus avoiding the sort.
795+
</p>
790796
</li><li>Precompile SQL functions to avoid overhead
791797
</li><li>Create utility to compute accurate random_page_cost value
792798
</li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG

0 commit comments

Comments
 (0)