PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (bruce@momjian.us)

Last updated:Mon Oct 23 22:41:16 EDT 2006

Last updated:Mon Oct 23 22:42:19 EDT 2006

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

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.

http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php

* Add estimated_count(*) to return an estimate of COUNT(*)

This would use the planner ANALYZE statistics to return an estimated

count.

http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php

* Allow data to be pulled directly from indexes

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>

Last updated: Mon Oct 23 22:41:16 EDT 2006

Last updated: Mon Oct 23 22:42:19 EDT 2006

<p>The most recent version of this document can be viewed at<br/>

<ahref="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.

<ahref="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>

</li><li>Add estimated_count(*) to return an estimate of COUNT(*)

<p> This would use the planner ANALYZE statistics to return an estimated

count.

<ahref="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>

</li><li>Allow data to be pulled directly from indexes

<p> Currently indexes do not have enough tuple visibility information