From ccbb07d92229a3ebdfbb129aafaba99a22658403 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 22 Apr 2005 15:40:16 +0000
Subject: 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/src/FAQ/TODO.html | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
(limited to 'doc/src')
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 @@
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.
@@ -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: