|
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:Wed Nov16 13:44:51 EST 2005 |
| 11 | +Last updated:Tue Nov22 17:53:39 EST 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>. |
@@ -762,6 +762,10 @@ <h1><a name="section_15">Cache Usage</a></h1> |
762 | 762 | get a count directly from a unique index, but for this to be |
763 | 763 | faster than a sequential scan it must avoid access to the heap |
764 | 764 | to obtain tuple visibility information. |
| 765 | +</p> |
| 766 | +</li><li>Add estimated_count(*) to return an estimate of COUNT(*) |
| 767 | +<p> This would use the planner ANALYZE statistatics to return an estimated |
| 768 | + count. |
765 | 769 | </p> |
766 | 770 | </li><li>Allow data to be pulled directly from indexes |
767 | 771 | <p> Currently indexes do not have enough tuple visibility information |
|