From 9204980aa180cecd0041d740b703fe54bb88f143 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 13 Apr 2006 10:50:13 +0000 Subject: 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. --- doc/src/FAQ/TODO.html | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 27f70ed7394..8f526802f2d 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-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 -- cgit v1.2.3