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

Commitcda598e

Browse files
committed
Move item to proper section:
< * 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. 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.<> * 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. 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 parent012786a commitcda598e

File tree

2 files changed

+16
-17
lines changed

2 files changed

+16
-17
lines changed

‎doc/TODO‎

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
PostgreSQL TODO List
22
====================
33
Current maintainer:Bruce Momjian (bruce@momjian.us)
4-
Last updated:Sun Dec1620:40:44 EST 2007
4+
Last updated:Fri Dec21 16:20:21 EST 2007
55

66
The most recent version of this document can be viewed at
77
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1232,14 +1232,6 @@ Startup Time Improvements
12321232
Solaris) might benefit from threading. Also explore the idea of
12331233
a single session using multiple threads to execute a statement faster.
12341234

1235-
* Experiment with multi-threaded backend better resource utilization
1236-
1237-
This would allow a single query to make use of multiple CPU's or
1238-
multiple I/O channels simultaneously. One idea is to create a
1239-
background reader that can pre-fetch sequential and index scan
1240-
pages needed by other backends. This could be expanded to allow
1241-
concurrent reads from multiple devices in a partitioned table.
1242-
12431235
* Add connection pooling
12441236

12451237
It is unclear if this should be done inside the backend code or done
@@ -1391,6 +1383,13 @@ Miscellaneous Performance
13911383

13921384
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
13931385

1386+
* Experiment with multi-threaded backend better resource utilization
1387+
1388+
This would allow a single query to make use of multiple CPU's or
1389+
multiple I/O channels simultaneously. One idea is to create a
1390+
background reader that can pre-fetch sequential and index scan
1391+
pages needed by other backends. This could be expanded to allow
1392+
concurrent reads from multiple devices in a partitioned table.
13941393

13951394

13961395
Source Code

‎doc/src/FAQ/TODO.html‎

Lines changed: 8 additions & 8 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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated:Sun Dec1620:40:44 EST 2007
11+
Last updated:Fri Dec21 16:20:21 EST 2007
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>.
@@ -1090,13 +1090,6 @@ <h1><a name="section_15">Startup Time Improvements</a></h1>
10901090
database startup overhead, but a few operating systems (Win32,
10911091
Solaris) might benefit from threading. Also explore the idea of
10921092
a single session using multiple threads to execute a statement faster.
1093-
</p>
1094-
</li><li>Experiment with multi-threaded backend better resource utilization
1095-
<p> This would allow a single query to make use of multiple CPU's or
1096-
multiple I/O channels simultaneously. One idea is to create a
1097-
background reader that can pre-fetch sequential and index scan
1098-
pages needed by other backends. This could be expanded to allow
1099-
concurrent reads from multiple devices in a partitioned table.
11001093
</p>
11011094
</li><li>Add connection pooling
11021095
<p> It is unclear if this should be done inside the backend code or done
@@ -1230,6 +1223,13 @@ <h1><a name="section_18">Miscellaneous Performance</a></h1>
12301223
</p>
12311224
</li><li>Consider reducing memory used for shared buffer reference count
12321225
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php</a>
1226+
</p>
1227+
</li><li>Experiment with multi-threaded backend better resource utilization
1228+
<p> This would allow a single query to make use of multiple CPU's or
1229+
multiple I/O channels simultaneously. One idea is to create a
1230+
background reader that can pre-fetch sequential and index scan
1231+
pages needed by other backends. This could be expanded to allow
1232+
concurrent reads from multiple devices in a partitioned table.
12331233
</p>
12341234
</li></ul>
12351235
<h1><aname="section_19">Source Code</a></h1>

0 commit comments

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