PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Sat Apr 23 17:43:18 EDT 2005
+Last updated: Sat Apr 23 17:44:43 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
* Add a script to ask system configuration questions and tune postgresql.conf
* Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
-* Consider parallel processing a single query
-
- This would involve using multiple threads or processes to do optimization,
- sorting, or execution of single query. The major advantage of such a
- feature would be to allow multiple CPUs to work together to process a
- single query.
-
* Research the use of larger page sizes
<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 23 17:43:18 EDT 2005
+Last updated: Sat Apr 23 17:44:43 EDT 2005
</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>.
</li><li>Add a script to ask system configuration questions and tune postgresql.conf
</li><li>Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
- </li><li>Consider parallel processing a single query
-<p> This would involve using multiple threads or processes to do optimization,
- sorting, or execution of single query. The major advantage of such a
- feature would be to allow multiple CPUs to work together to process a
- single query.
-</p>
</li><li>Research the use of larger page sizes
</li></ul>
<h1><a name="section_20">Source Code</a></h1>
OSDN Git Service
