From 9204980aa180cecd0041d740b703fe54bb88f143 Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Thu, 13 Apr 2006 10:50:13 +0000 Subject: [PATCH] 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/TODO | 7 +++++-- doc/src/FAQ/TODO.html | 7 +++++-- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/doc/TODO b/doc/TODO index 85c9ac576b4..aa3b31b683c 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: 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 27f70ed7394..8f526802f2d 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@ <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <h1><a name="section_1">PostgreSQL TODO List</a></h1> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> -Last updated: Mon Apr 10 22:08:01 EDT 2006 +Last updated: Thu Apr 13 06:50:02 EDT 2006 </p> <p>The most recent version of this document can be viewed at<br/> <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. @@ -915,7 +915,10 @@ first. </p> </li><li>Experiment with multi-threaded backend better resource utilization <p> 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. </p> </li><li>Add connection pooling <p> It is unclear if this should be done inside the backend code or done -- GitLab