From a3e3389913b47cc600d0588fe395da976b61806c Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 8 Jun 2007 18:45:22 +0000 Subject: [PATCH] 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 < --- doc/TODO | 15 ++------------- doc/src/FAQ/TODO.html | 14 ++------------ 2 files changed, 4 insertions(+), 25 deletions(-) diff --git a/doc/TODO b/doc/TODO index ac83213c36b..dd9d0c1b143 100644 --- a/doc/TODO +++ b/doc/TODO @@ -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 @@

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. @@ -1010,18 +1010,8 @@ first. There is also a developer's wiki at

  • Query execute plan
  • 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