Update:

<   multiple I/O channels simultaneously.
>   multiple I/O channels simultaneously.  One idea is to create a
>   background reader that can pre-fetch sequential and index scan
>   pages needed by other backends.  This could be expanded to allow
>   concurrent reads from multiple devices in a partitioned table.

diff --git a/doc/TODO b/doc/TODO
index 85c9ac576b45ce208d3cd77a3ddefb17a2c2ec94..aa3b31b683cce616ffa90ba16ccc599829c06120 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Mon Apr 10 22:08:01 EDT 2006
+Last updated:      Thu Apr 13 06:50:02 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1012,7 +1012,10 @@ Startup Time Improvements
 * Experiment with multi-threaded backend better resource utilization
 
   This would allow a single query to make use of multiple CPU's or
-  multiple I/O channels simultaneously.
+  multiple I/O channels simultaneously.  One idea is to create a
+  background reader that can pre-fetch sequential and index scan
+  pages needed by other backends.  This could be expanded to allow
+  concurrent reads from multiple devices in a partitioned table.
 
 * Add connection pooling
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 27f70ed73949f4d81cb84c571f3fcf13604dc324..8f526802f2dc6c63c44aac4533d18afc9d3aa14c 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:           Mon Apr 10 22:08:01 EDT 2006
+Last updated:           Thu Apr 13 06:50:02 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -915,7 +915,10 @@ first.
 
   Experiment with multi-threaded backend better resource utilization
   This would allow a single query to make use of multiple CPU's or
-  multiple I/O channels simultaneously.
+  multiple I/O channels simultaneously.  One idea is to create a
+  background reader that can pre-fetch sequential and index scan
+  pages needed by other backends.  This could be expanded to allow
+  concurrent reads from multiple devices in a partitioned table.
 
   Add connection pooling
   It is unclear if this should be done inside the backend code or done