Fix typo:

<   Currently indexes do not have enough tuple tuple visibility
<   information to allow data to be pulled from the index without
<   also accessing the heap.  One way to allow this is to set a bit
<   to index tuples to indicate if a tuple is currently visible to
<   all transactions when the first valid heap lookup happens.  This
<   bit would have to be cleared when a heap tuple is expired.
>   Currently indexes do not have enough tuple visibility information
>   to allow data to be pulled from the index without also accessing
>   the heap.  One way to allow this is to set a bit to index tuples
>   to indicate if a tuple is currently visible to all transactions
>   when the first valid heap lookup happens.  This bit would have to
>   be cleared when a heap tuple is expired.

diff --git a/doc/TODO b/doc/TODO
index f0d4b0a53891b3a279eeda253ec5a38a110406c0..869ed44eb6f9a02b4879bd6fa19d4f418d176d7e 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Fri Apr 22 09:38:10 EDT 2005
+Last updated:      Fri Apr 22 11:40:08 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -714,12 +714,12 @@ Cache
 
 * Allow data to be pulled directly from indexes
 
-  Currently indexes do not have enough tuple tuple visibility
-  information to allow data to be pulled from the index without
-  also accessing the heap.  One way to allow this is to set a bit
-  to index tuples to indicate if a tuple is currently visible to
-  all transactions when the first valid heap lookup happens.  This 
-  bit would have to be cleared when a heap tuple is expired.
+  Currently indexes do not have enough tuple visibility information 
+  to allow data to be pulled from the index without also accessing 
+  the heap.  One way to allow this is to set a bit to index tuples 
+  to indicate if a tuple is currently visible to all transactions 
+  when the first valid heap lookup happens.  This bit would have to 
+  be cleared when a heap tuple is expired.
 
 * Consider automatic caching of queries at various levels:
    o Parsed query tree

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index ce69fbc7521d4a239115526f921ab4f5ecbd44b0..aff4799b8c1875e48cdcf756a854bc4562219e42 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:           Fri Apr 22 09:38:10 EDT 2005
+Last updated:           Fri Apr 22 11:40:08 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -653,12 +653,12 @@ first.
   to obtain tuple visibility information.
 
   Allow data to be pulled directly from indexes
-  Currently indexes do not have enough tuple tuple visibility
-  information to allow data to be pulled from the index without
-  also accessing the heap.  One way to allow this is to set a bit
-  to index tuples to indicate if a tuple is currently visible to
-  all transactions when the first valid heap lookup happens.  This 
-  bit would have to be cleared when a heap tuple is expired.
+  Currently indexes do not have enough tuple visibility information 
+  to allow data to be pulled from the index without also accessing 
+  the heap.  One way to allow this is to set a bit to index tuples 
+  to indicate if a tuple is currently visible to all transactions 
+  when the first valid heap lookup happens.  This bit would have to 
+  be cleared when a heap tuple is expired.
 
   Consider automatic caching of queries at various levels: