Add TODO:

>
> * Improve performance of shared invalidation queue for multiple CPUs
>
>   http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php
This commit is contained in:
Bruce Momjian 2008-03-22 01:44:42 +00:00
parent 3892dc75eb
commit 4edb822360
2 changed files with 9 additions and 2 deletions

View File

@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Fri Mar 21 21:30:06 EDT 2008
Last updated: Fri Mar 21 21:44:38 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -1662,6 +1662,10 @@ Miscellaneous Performance
http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php
* Improve performance of shared invalidation queue for multiple CPUs
http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php
* Consider Cartesian joins when both relations are needed to form an
indexscan qualification for a third relation

View File

@ -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: Fri Mar 21 21:30:06 EDT 2008
Last updated: Fri Mar 21 21:44:38 EDT 2008
</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>.
@ -1440,6 +1440,9 @@ first. There is also a developer's wiki at<br/>
</li><li>Consider if CommandCounterIncrement() can avoid its
AcceptInvalidationMessages() call
<p> <a href="http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php">http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php</a>
</p>
</li><li>Improve performance of shared invalidation queue for multiple CPUs
<p> <a href="http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php">http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php</a>
</p>
</li><li>Consider Cartesian joins when both relations are needed to form an
indexscan qualification for a third relation