PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Wed Nov 16 13:44:51 EST 2005
+Last updated: Tue Nov 22 17:53:39 EST 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
faster than a sequential scan it must avoid access to the heap
to obtain tuple visibility information.
+* Add estimated_count(*) to return an estimate of COUNT(*)
+
+ This would use the planner ANALYZE statistatics to return an estimated
+ count.
+
* Allow data to be pulled directly from indexes
Currently indexes do not have enough tuple visibility information
<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: Wed Nov 16 13:44:51 EST 2005
+Last updated: Tue Nov 22 17:53:39 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>.
get a count directly from a unique index, but for this to be
faster than a sequential scan it must avoid access to the heap
to obtain tuple visibility information.
+</p>
+ </li><li>Add estimated_count(*) to return an estimate of COUNT(*)
+<p> This would use the planner ANALYZE statistatics to return an estimated
+ count.
</p>
</li><li>Allow data to be pulled directly from indexes
<p> Currently indexes do not have enough tuple visibility information
projects / postgresql / commitdiff