Add TODO items we don't want (Idea from Josh Berkus)
> > > Features We Do _Not_ Want > ========================= > > * All backends running as threads in a single process (not want) > > This eliminates the process protection we get from the current setup. > Thread creation is usually the same overhead as process creation on > modern systems, so it seems unwise to use a pure threaded model. > > * Optimizer hints (not want) > > Optimizer hints are used to work around problems in the optimizer. We > would rather have the problems reported and fixed. > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
This commit is contained in:
parent
4f81337d9d
commit
c7fa4aa3e7
18
doc/TODO
18
doc/TODO
@ -2,7 +2,7 @@
|
||||
PostgreSQL TODO List
|
||||
====================
|
||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||
Last updated: Wed Aug 9 10:55:32 EDT 2006
|
||||
Last updated: Wed Aug 9 12:35:39 EDT 2006
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
||||
@ -1427,6 +1427,22 @@ Source Code
|
||||
of result sets using new statement protocol
|
||||
|
||||
|
||||
Features We Do _Not_ Want
|
||||
=========================
|
||||
|
||||
* All backends running as threads in a single process (not want)
|
||||
|
||||
This eliminates the process protection we get from the current setup.
|
||||
Thread creation is usually the same overhead as process creation on
|
||||
modern systems, so it seems unwise to use a pure threaded model.
|
||||
|
||||
* Optimizer hints (not want)
|
||||
|
||||
Optimizer hints are used to work around problems in the optimizer. We
|
||||
would rather have the problems reported and fixed.
|
||||
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
|
||||
|
||||
|
||||
---------------------------------------------------------------------------
|
||||
|
||||
|
||||
|
@ -8,7 +8,7 @@
|
||||
<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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
||||
Last updated: Wed Aug 9 10:55:32 EDT 2006
|
||||
Last updated: Wed Aug 9 12:35:39 EDT 2006
|
||||
</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>.
|
||||
@ -1287,9 +1287,23 @@ first.
|
||||
of result sets using new statement protocol
|
||||
</li></ul>
|
||||
</li></ul>
|
||||
<h1><a name="section_23">Features We Do _Not_ Want</a></h1>
|
||||
|
||||
<ul>
|
||||
<li>All backends running as threads in a single process (not want)
|
||||
<p> This eliminates the process protection we get from the current setup.
|
||||
Thread creation is usually the same overhead as process creation on
|
||||
modern systems, so it seems unwise to use a pure threaded model.
|
||||
</p>
|
||||
</li><li>Optimizer hints (not want)
|
||||
<p> Optimizer hints are used to work around problems in the optimizer. We
|
||||
would rather have the problems reported and fixed.
|
||||
<a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php</a>
|
||||
</p>
|
||||
</li></ul>
|
||||
<hr/>
|
||||
|
||||
<h2><a name="section_22_1">Developers who have claimed items are:</a></h2>
|
||||
<h2><a name="section_23_1">Developers who have claimed items are:</a></h2>
|
||||
<ul>
|
||||
<li>Alvaro is Alvaro Herrera <<a href="mailto:alvherre@dcc.uchile.cl">alvherre@dcc.uchile.cl</a>>
|
||||
</li><li>Andrew is Andrew Dunstan <<a href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>>
|
||||
|
Loading…
x
Reference in New Issue
Block a user