From fb2b198609418db394d150ce43b8e37aa0d8f017 Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Sun, 9 Apr 2006 20:24:30 +0000 Subject: [PATCH] Add: < * Experiment with multi-threaded backend [thread] > * Experiment with multi-threaded backend for backend creation [thread] 1003a1004,1008 > > * 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. --- doc/TODO | 9 +++++++-- doc/src/FAQ/TODO.html | 8 ++++++-- 2 files changed, 13 insertions(+), 4 deletions(-) diff --git a/doc/TODO b/doc/TODO index d788d34ceee..ded45159158 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: Sat Apr 8 23:26:57 EDT 2006 +Last updated: Sun Apr 9 16:24:16 EDT 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -994,7 +994,7 @@ Locking Startup Time Improvements ========================= -* Experiment with multi-threaded backend [thread] +* Experiment with multi-threaded backend for backend creation [thread] This would prevent the overhead associated with process creation. Most operating systems have trivial process creation time compared to @@ -1002,6 +1002,11 @@ 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. + * Add connection pooling It is unclear if this should be done inside the backend code or done diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 9091a9accf5..878ee6218ce 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: Sat Apr 8 23:26:57 EDT 2006 +Last updated: Sun Apr 9 16:24:16 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>. @@ -900,12 +900,16 @@ first. <h1><a name="section_18">Startup Time Improvements</a></h1> <ul> - <li>Experiment with multi-threaded backend [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>] + <li>Experiment with multi-threaded backend for backend creation [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>] <p> This would prevent the overhead associated with process creation. Most operating systems have trivial process creation time compared to 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. +</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. </p> </li><li>Add connection pooling <p> It is unclear if this should be done inside the backend code or done -- GitLab