Skip to content

P
Postgres FD Implementation
Commit 754838ca authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Done: 

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

Not needed anymore:

< * Reuse index tuples that point to heap tuples that are not visible to
<   anyone?
parent ad8fbb54
Show whitespace changes
Inline Side-by-side
Showing with 8 additions and 36 deletions
doc/TODO
View file @ 754838ca
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Fri Sep 14 15:02:41 EDT 2007 Last updated: Thu Sep 20 14:53:32 EDT 2007
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -1208,24 +1208,9 @@ Vacuum ...@@ -1208,24 +1208,9 @@ Vacuum
in hopes that empty pages at the end can be truncated by VACUUM 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 * Allow FSM page return free space based on table clustering, to assist
in maintaining clustering? in maintaining clustering?
* Consider shrinking expired tuples to just their headers * -Consider shrinking expired tuples to just their headers
* -Allow heap reuse of UPDATEd rows if no indexed columns are changed,
http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php and old and new versions are on the same heap page
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?
* Improve dead row detection during multi-statement transactions usage * Improve dead row detection during multi-statement transactions usage
http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php
......
doc/src/FAQ/TODO.html
View file @ 754838ca
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Fri Sep 14 15:02:41 EDT 2007 Last updated: Thu Sep 20 14:53:32 EDT 2007
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -1075,22 +1075,9 @@ first. There is also a developer's wiki at<br/> ...@@ -1075,22 +1075,9 @@ first. There is also a developer's wiki at<br/>
in hopes that empty pages at the end can be truncated by VACUUM 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 </li><li>Allow FSM page return free space based on table clustering, to assist
in maintaining clustering? in maintaining clustering?
</li><li>Consider shrinking expired tuples to just their headers </li><li>-<em>Consider shrinking expired tuples to just their headers</em>
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php</a> </li><li>-<em>Allow heap reuse of UPDATEd rows if no indexed columns are changed,</em>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php</a> and old and new versions are on the same heap page
</p>
</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>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php</a>
</p>
</li><li>Reuse index tuples that point to heap tuples that are not visible to
anyone?
</li><li>Improve dead row detection during multi-statement transactions usage </li><li>Improve dead row detection during multi-statement transactions usage
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php</a> <p> <a href="http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php</a>
</p> </p>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment