From cda598e184a10dad79a75ecc9ac1e77c1fededd7 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 21 Dec 2007 21:20:27 +0000
Subject: 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.
---
doc/src/FAQ/TODO.html | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index b10c4a9fb2e..1f509dc7391 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (bruce@momjian.us)
-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.
--
cgit v1.2.3