postgres.git / summary / log / commit / refs
commit ccbb07d92229a3ebdfbb129aafaba99a22658403
Author: Bruce Momjian <bruce@momjian.us>
Date: Fri Apr 22 15:40:16 2005 +0000
First released in: 8.1.0
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.
doc/TODO | 14 +++++++-------
doc/src/FAQ/TODO.html | 14 +++++++-------
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index f0d4b0a5389..869ed44eb6f 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-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 ce69fbc7521..aff4799b8c1 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Fri Apr 22 09:38:10 EDT 2005
+Last updated: Fri Apr 22 11:40:08 EDT 2005
</p>
<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>.
@@ -653,12 +653,12 @@ first.
to obtain tuple visibility information.
</p>
</li><li>Allow data to be pulled directly from indexes
-<p> 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.
+<p> 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.
</p>
</li><li>Consider automatic caching of queries at various levels:
<ul>
[parent: 6f61ddd40d77]