Move item to proper section:

< * 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.  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.
<
> * 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.  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 a7084775590a38aa67544b4a261f31c2b291cde2..1babc4a24541b4e095bf8ea5cd03ce32ac273e09 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Sun Dec 16 20:40:44 EST 2007
+Last updated:      Fri Dec 21 16:20:21 EST 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1232,14 +1232,6 @@ Startup Time Improvements
   Solaris) might benefit from threading.  Also explore the idea of
   a single session using multiple threads to execute a statement faster.
 
-* 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.  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
@@ -1391,6 +1383,13 @@ Miscellaneous Performance
 
   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
 
+* 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.  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.
 
 
 Source Code

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index b10c4a9fb2ee8ebe4312c714b3a6d5ee2d52b08b..1f509dc73910bcbe7caa2b156d9798f7a6b09528 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:           Sun Dec 16 20:40:44 EST 2007
+Last updated:           Fri Dec 21 16:20:21 EST 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1090,13 +1090,6 @@ first.  There is also a developer's wiki at
   database startup overhead, but a few operating systems (Win32,
   Solaris) might benefit from threading.  Also explore the idea of
   a single session using multiple threads to execute a statement faster.
-
-  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.  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
@@ -1230,6 +1223,13 @@ first.  There is also a developer's wiki at
 
   Consider reducing memory used for shared buffer reference count
   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
+
+  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.  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.
 
 
 Source Code