Skip to content

P
Postgres FD Implementation
Commit 2f2b58d6 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Spit items: 

* Experiment with multi-threaded backend better I/O utilization

  This would allow a single query to make use of 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 CPU utilization

  This would allow several CPUs to be used for a single query, such as
  for sorting or query execution.
parent 8426b564
Show whitespace changes
Inline Side-by-side
Showing with 23 additions and 14 deletions
doc/TODO
View file @ 2f2b58d6
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Tue Mar 18 19:32:48 EDT 2008 Last updated: Tue Mar 18 19:35:12 EDT 2008
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.
...@@ -1630,13 +1630,18 @@ Miscellaneous Performance ...@@ -1630,13 +1630,18 @@ Miscellaneous Performance
http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php
* Experiment with multi-threaded backend better resource utilization * Experiment with multi-threaded backend better I/O 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 I/O channels
multiple I/O channels simultaneously. One idea is to create a simultaneously. One idea is to create a background reader that can
background reader that can pre-fetch sequential and index scan pre-fetch sequential and index scan pages needed by other backends.
pages needed by other backends. This could be expanded to allow This could be expanded to allow concurrent reads from multiple devices
concurrent reads from multiple devices in a partitioned table. in a partitioned table.
* Experiment with multi-threaded backend better CPU utilization
This would allow several CPUs to be used for a single query, such as
for sorting or query execution.
* Consider increasing the minimum allowed number of shared buffers * Consider increasing the minimum allowed number of shared buffers
......
doc/src/FAQ/TODO.html
View file @ 2f2b58d6
...@@ -8,7 +8,7 @@ ...@@ -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:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Tue Mar 18 19:32:48 EDT 2008 Last updated: Tue Mar 18 19:35:12 EDT 2008
</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>.
...@@ -1415,12 +1415,16 @@ first. There is also a developer's wiki at<br/> ...@@ -1415,12 +1415,16 @@ first. There is also a developer's wiki at<br/>
</p> </p>
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php">http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php</a> <p> <a href="http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php">http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php</a>
</p> </p>
</li><li>Experiment with multi-threaded backend better resource utilization </li><li>Experiment with multi-threaded backend better I/O 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 I/O channels
multiple I/O channels simultaneously. One idea is to create a simultaneously. One idea is to create a background reader that can
background reader that can pre-fetch sequential and index scan pre-fetch sequential and index scan pages needed by other backends.
pages needed by other backends. This could be expanded to allow This could be expanded to allow concurrent reads from multiple devices
concurrent reads from multiple devices in a partitioned table. in a partitioned table.
</p>
</li><li>Experiment with multi-threaded backend better CPU utilization
<p> This would allow several CPUs to be used for a single query, such as
for sorting or query execution.
</p> </p>
</li><li>Consider increasing the minimum allowed number of shared buffers </li><li>Consider increasing the minimum allowed number of shared buffers
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php">http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php</a> <p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php">http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php</a>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment