Update:

< * Add missing rtree optimizer selectivity > * Improve selectivity functions for geometric operators

Update:
< * Add missing rtree optimizer selectivity > * Improve selectivity functions for geometric operators
e135d963 · Bruce Momjian · eb29d89f · e135d963 · e135d963
Commit e135d963 authored Dec 29, 2005 by Bruce Momjian
Hide whitespace changes
Inline Side-by-side

Showing with 4 additions and 4 deletions

doc/TODO doc/TODO +2 -2

doc/src/FAQ/TODO.html doc/src/FAQ/TODO.html +2 -2

No files found.
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated:		Tue Dec 27 22:59:37 EST 2005
+Last updated:		Thu Dec 29 11:45:08 EST 2005

 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1018,7 +1018,7 @@ Write-Ahead Log
 Optimizer / Executor
 ====================

-* Add missing rtree optimizer selectivity
+* Improve selectivity functions for geometric operators
 * Allow ORDER BY ... LIMIT # to select high/low value without sort or
  index using a sequential scan for highest/lowest values


--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
 <h1><a name="section_1">PostgreSQL TODO List</a></h1>
 <p>Current maintainer:     Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated:           Tue Dec 27 22:59:37 EST 2005
+Last updated:           Thu Dec 29 11:45:08 EST 2005
 </p>
 <p>The most recent version of this document can be viewed at<br/>
 <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -923,7 +923,7 @@ first.
 <h1><a name="section_20">Optimizer / Executor</a></h1>

 <ul>
-  <li>Add missing rtree optimizer selectivity
+  <li>Improve selectivity functions for geometric operators
  </li><li>Allow ORDER BY ... LIMIT # to select high/low value without sort or
  index using a sequential scan for highest/lowest values
 <p>  Right now, if no index exists, ORDER BY ... LIMIT # requires we sort