Add:

> * Research storing only active XIDs in subtransaction cache

diff --git a/doc/TODO b/doc/TODO
index 66b8ddd5bf65aef07efbe661f17f22f267789272..2e36619828a275a14b3358a6e507029d89cfc76c 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Thu Sep 14 14:10:31 EDT 2006
+Last updated:      Thu Sep 14 16:30:31 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1353,6 +1353,7 @@ Miscellaneous Performance
   cmin/cmax pair and is stored in local memory.  Another idea is to
   store both cmin and cmax only in local memory.
 
+* Research storing only active XIDs in subtransaction cache
 * Consider ways of storing rows more compactly on disk
 
    o Reorder physical storage order to reduce padding?

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 25d66b504411d14ff7a08c59a4fbe27f00613f2a..3820a412e33573a54e92e248a07ffd6b49196746 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Thu Sep 14 14:10:31 EDT 2006
+Last updated:           Thu Sep 14 16:30:31 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1219,6 +1219,7 @@ first.
   cmin/cmax pair and is stored in local memory.  Another idea is to
   store both cmin and cmax only in local memory.
 
+  Research storing only active XIDs in subtransaction cache
   Consider ways of storing rows more compactly on disk
   
     Reorder physical storage order to reduce padding?