PostgreSQL TODO List

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

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

Last updated:Fri Sep14 15:02:41 EDT 2007

Last updated:Thu Sep20 14:53:32 EDT 2007

The most recent version of this document can be viewed at

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

in hopes that empty pages at the end can be truncated by VACUUM

* Allow FSM page return free space based on table clustering, to assist

in maintaining clustering?

* Consider shrinking expired tuples to just their headers

http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php

http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php

* Allow heap reuse of UPDATEd rows if no indexed columns are changed,

and old and new versions are on the same heap page?

While vacuum handles DELETEs fine, updating of non-indexed columns, like

counters, are difficult for VACUUM to handle efficiently. This method

is possible for same-page updates because a single index row can be

used to point to both old and new values.

http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php

http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php

* Reuse index tuples that point to heap tuples that are not visible to

anyone?

* -Consider shrinking expired tuples to just their headers

* -Allow heap reuse of UPDATEd rows if no indexed columns are changed,

and old and new versions are on the same heap page

* Improve dead row detection during multi-statement transactions usage

http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php

<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:Fri Sep14 15:02:41 EDT 2007

Last updated:Thu Sep20 14:53:32 EDT 2007

<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>.

in hopes that empty pages at the end can be truncated by VACUUM

</li><li>Allow FSM page return free space based on table clustering, to assist

in maintaining clustering?

</li><li>Consider shrinking expired tuples to just their headers

<p><ahref="http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php</a>

<ahref="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php</a>

</li><li>Allow heap reuse of UPDATEd rows if no indexed columns are changed,

and old and new versions are on the same heap page?

<p> While vacuum handles DELETEs fine, updating of non-indexed columns, like

counters, are difficult for VACUUM to handle efficiently. This method

is possible for same-page updates because a single index row can be

used to point to both old and new values.

<p><ahref="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php</a>

<ahref="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php</a>

</li><li>Reuse index tuples that point to heap tuples that are not visible to

anyone?

</li><li>-<em>Consider shrinking expired tuples to just their headers</em>

</li><li>-<em>Allow heap reuse of UPDATEd rows if no indexed columns are changed,</em>

and old and new versions are on the same heap page

</li><li>Improve dead row detection during multi-statement transactions usage

<p><ahref="http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php</a>