summaryrefslogtreecommitdiff
path: root/doc/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'doc/TODO')
-rw-r--r--doc/TODO11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/TODO b/doc/TODO
index 22c6e3c461..c3bf43a5f8 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: Thu Dec 1 17:12:27 EST 2005
+Last updated: Thu Dec 1 17:30:23 EST 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -859,11 +859,14 @@ Cache Usage
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
+ the heap. One way to allow this is to set a bit on 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.
-
+ be cleared when a heap tuple is expired. Another idea is to maintain
+ a bitmap of heap pages where all rows are visible to all backends,
+ and allow index lookups to reference that bitmap to avoid heap
+ lookups, perhaps the same bitmap we might add someday to determine
+ which heap pages need vacuuming.
* Consider automatic caching of queries at various levels: