Merge items:

< This would be beneficial when there are few distinct values. > This would be beneficial when there are few distinct values. This is > already used by GROUP BY. 946d946 < * Allow DISTINCT to use hashing like GROUP BY
21 years ago · 8d86982a11
parent b7159824e6
commit 8d86982a11
2 changed files with 6 additions and 6 deletions
--- a/doc/TODO
+++ b/doc/TODO
@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated:		Mon Sep 19 22:21:26 EDT 2005
+Last updated:		Tue Sep 20 16:51:26 EDT 2005

 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@ -939,11 +939,11 @@ Optimizer / Executor
 * Have EXPLAIN ANALYZE highlight poor optimizer estimates
 * Consider using hash buckets to do DISTINCT, rather than sorting

-  This would be beneficial when there are few distinct values.
+  This would be beneficial when there are few distinct values.  This is
+  already used by GROUP BY.

 * Log queries where the optimizer row estimates were dramatically
  different from the number of rows actually found?
-* Allow DISTINCT to use hashing like GROUP BY


 Miscellaneous Performance
--- 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:           Mon Sep 19 22:21:26 EDT 2005
+Last updated:           Tue Sep 20 16:51:26 EDT 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>.
@ -851,11 +851,11 @@ first.
  </li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
  </li><li>Have EXPLAIN ANALYZE highlight poor optimizer estimates
  </li><li>Consider using hash buckets to do DISTINCT, rather than sorting
-<p>  This would be beneficial when there are few distinct values.
+<p>  This would be beneficial when there are few distinct values.  This is
+  already used by GROUP BY.
 </p>
  </li><li>Log queries where the optimizer row estimates were dramatically
  different from the number of rows actually found?
-  </li><li>Allow DISTINCT to use hashing like GROUP BY
 </li></ul>
 <h1><a name="section_21">Miscellaneous Performance</a></h1>