|
8 | 8 | <bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF"> |
9 | 9 | <h1><aname="section_1">PostgreSQL TODO List</a></h1> |
10 | 10 | <p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> |
11 | | -Last updated:Mon Sep19 22:21:26 EDT 2005 |
| 11 | +Last updated:Tue Sep20 16:51:26 EDT 2005 |
12 | 12 | </p> |
13 | 13 | <p>The most recent version of this document can be viewed at<br/> |
14 | 14 | <ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. |
@@ -851,11 +851,11 @@ <h1><a name="section_20">Optimizer / Executor</a></h1> |
851 | 851 | </li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG |
852 | 852 | </li><li>Have EXPLAIN ANALYZE highlight poor optimizer estimates |
853 | 853 | </li><li>Consider using hash buckets to do DISTINCT, rather than sorting |
854 | | -<p> This would be beneficial when there are few distinct values. |
| 854 | +<p> This would be beneficial when there are few distinct values. This is |
| 855 | + already used by GROUP BY. |
855 | 856 | </p> |
856 | 857 | </li><li>Log queries where the optimizer row estimates were dramatically |
857 | 858 | different from the number of rows actually found? |
858 | | -</li><li>Allow DISTINCT to use hashing like GROUP BY |
859 | 859 | </li></ul> |
860 | 860 | <h1><aname="section_21">Miscellaneous Performance</a></h1> |
861 | 861 |
|
|