pgsql: Done: < * Allow sequential scans to take advantage of other - Mailing list pgsql-committers

From momjian@postgresql.org (Bruce Momjian)
Subject pgsql: Done: < * Allow sequential scans to take advantage of other
Date
Msg-id 20070608184522.BC85B9FC26A@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
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
<

Modified Files:
--------------
    pgsql/doc:
        TODO (r1.2200 -> r1.2201)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2200&r2=1.2201)
    pgsql/doc/src/FAQ:
        TODO.html (r1.701 -> r1.702)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.701&r2=1.702)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Arrange for large sequential scans to synchronize with each
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add note that LIMIT without ORDER BY can produce outright