Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit9204980

Browse files
committed
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.
1 parent49a7610 commit9204980

File tree

2 files changed

+10
-4
lines changed

2 files changed

+10
-4
lines changed

‎doc/TODO

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Mon Apr10 22:08:01 EDT 2006
5+
Last updated:Thu Apr13 06:50:02 EDT 2006
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1012,7 +1012,10 @@ Startup Time Improvements
10121012
* Experiment with multi-threaded backend better resource utilization
10131013

10141014
This would allow a single query to make use of multiple CPU's or
1015-
multiple I/O channels simultaneously.
1015+
multiple I/O channels simultaneously. One idea is to create a
1016+
background reader that can pre-fetch sequential and index scan
1017+
pages needed by other backends. This could be expanded to allow
1018+
concurrent reads from multiple devices in a partitioned table.
10161019

10171020
* Add connection pooling
10181021

‎doc/src/FAQ/TODO.html

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11-
Last updated:Mon Apr10 22:08:01 EDT 2006
11+
Last updated:Thu Apr13 06:50:02 EDT 2006
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -915,7 +915,10 @@ <h1><a name="section_18">Startup Time Improvements</a></h1>
915915
</p>
916916
</li><li>Experiment with multi-threaded backend better resource utilization
917917
<p> This would allow a single query to make use of multiple CPU's or
918-
multiple I/O channels simultaneously.
918+
multiple I/O channels simultaneously. One idea is to create a
919+
background reader that can pre-fetch sequential and index scan
920+
pages needed by other backends. This could be expanded to allow
921+
concurrent reads from multiple devices in a partitioned table.
919922
</p>
920923
</li><li>Add connection pooling
921924
<p> It is unclear if this should be done inside the backend code or done

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp