|
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: Fri May 27 18:01:15 EDT 2005 |
| 11 | +Last updated: Fri May 27 18:07:21 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>. |
@@ -324,6 +324,10 @@ <h1><a name="section_6">Indexes</a></h1> |
324 | 324 | several hash buckets could be stored on a single page and greater |
325 | 325 | granularity used for the hash algorithm. |
326 | 326 | </p> |
| 327 | +</li><li>Consider sorting hash buckets so entries can be found using a binary |
| 328 | + search, rather than a linear scan |
| 329 | +</li><li>In hash indexes, consider storing the hash value with or instead |
| 330 | + of the key itself |
327 | 331 | </li><li>Allow accurate statistics to be collected on indexes with more than |
328 | 332 | one column or expression indexes, perhaps using per-index statistics |
329 | 333 | </li><li>Add fillfactor to control reserved free space during index creation |
|