database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-25 01:02:05 +03:00
Code Activity

Update:

Browse Source 
<   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.
This commit is contained in:
Bruce Momjian
2006-04-13 10:50:13 +00:00
parent 49a7610c36
commit 9204980aa1
2 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
@ -1012,7 +1012,10 @@ Startup Time Improvements
* Experiment with multi-threaded backend better resource utilization * Experiment with multi-threaded backend better resource utilization
This would allow a single query to make use of multiple CPU's or 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 * Add connection pooling

7
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <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>
<p>The most recent version of this document can be viewed at<br/> <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>. <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> </p>
</li><li>Experiment with multi-threaded backend better resource utilization </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 <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> </p>
</li><li>Add connection pooling </li><li>Add connection pooling
<p> It is unclear if this should be done inside the backend code or done <p> It is unclear if this should be done inside the backend code or done