diff options
| author | Bruce Momjian <bruce@momjian.us> | 2007-06-08 18:45:22 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2007-06-08 18:45:22 +0000 |
| commit | a3e3389913b47cc600d0588fe395da976b61806c (patch) | |
| tree | 4ad263491f190bda99d1a75aa10169ecc3c82c61 | |
| parent | a04a423599b347325f9a73dfb2d533b24e1cbab3 (diff) | |
| download | postgresql-a3e3389913b47cc600d0588fe395da976b61806c.tar.gz postgresql-a3e3389913b47cc600d0588fe395da976b61806c.zip | |
Done:
< * Allow sequential scans to take advantage of other concurrent
> * -Allow sequential scans to take advantage of other concurrent
<
< One possible implementation is to start sequential scans from the lowest
< numbered buffer in the shared cache, and when reaching the end wrap
< around to the beginning, rather than always starting sequential scans
< at the start of the table.
<
< http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php
< http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
< http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php
< http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php
<
| -rw-r--r-- | doc/TODO | 15 | ||||
| -rw-r--r-- | doc/src/FAQ/TODO.html | 14 |
2 files changed, 4 insertions, 25 deletions
@@ -1,7 +1,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sun Jun 3 14:49:04 EDT 2007 +Last updated: Fri Jun 8 14:45:14 EDT 2007 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1132,19 +1132,8 @@ Cache Usage o Query execute plan o Query results -* Allow sequential scans to take advantage of other concurrent +* -Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" - - One possible implementation is to start sequential scans from the lowest - numbered buffer in the shared cache, and when reaching the end wrap - around to the beginning, rather than always starting sequential scans - at the start of the table. - - http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php - http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php - http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php - http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php - * Consider increasing internal areas when shared buffers is increased http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index a36a8f0bfd1..7e9f745dd10 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -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: Sun Jun 3 14:49:04 EDT 2007 +Last updated: Fri Jun 8 14:45:14 EDT 2007 </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>. @@ -1010,18 +1010,8 @@ first. There is also a developer's wiki at<br/> </li><li>Query execute plan </li><li>Query results </li></ul> - </li><li>Allow sequential scans to take advantage of other concurrent + </li><li>-<em>Allow sequential scans to take advantage of other concurrent</em> sequential scans, also called "Synchronised Scanning" -<p> One possible implementation is to start sequential scans from the lowest - numbered buffer in the shared cache, and when reaching the end wrap - around to the beginning, rather than always starting sequential scans - at the start of the table. -</p> -<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php">http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php</a> - <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php</a> - <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php</a> - <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php</a> -</p> </li><li>Consider increasing internal areas when shared buffers is increased <p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php">http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php</a> </p> |