| From: | momjian(at)postgresql(dot)org (Bruce Momjian) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Done: < * Allow sequential scans to take advantage of other |
| Date: | 2007-06-08 18:45:22 |
| Message-ID: | 20070608184522.BC85B9FC26A@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-08 20:26:18 | pgsql: Add note that LIMIT without ORDER BY can produce outright |
| Previous Message | Tom Lane | 2007-06-08 18:23:53 | pgsql: Arrange for large sequential scans to synchronize with each |