This item was fixed in a different way, so has been removed:

<
< * Allow free-behind capability for large sequential scans to avoid
<   kernel cache spoiling
<
<   Posix_fadvise() can control both sequential/random file caching and
<   free-behind behavior, but it is unclear how the setting affects other
<   backends that also have the file open, and the feature is not supported
<   on all operating systems.

diff --git a/doc/TODO b/doc/TODO
index 4334a151675b27f439120523471ea9fe6757f4b5..18e0c871bbcc9ca206091e0af4502214f77ce3a0 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Fri Dec  7 12:52:05 EST 2007
+Last updated:      Wed Dec 12 01:59:39 EST 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1069,14 +1069,6 @@ Fsync
 Cache Usage
 ===========
 
-* Allow free-behind capability for large sequential scans to avoid
-  kernel cache spoiling
-
-  Posix_fadvise() can control both sequential/random file caching and
-  free-behind behavior, but it is unclear how the setting affects other
-  backends that also have the file open, and the feature is not supported
-  on all operating systems.
-
 * Speed up COUNT(*)
 
   We could use a fixed row count and a +/- count to follow MVCC

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 8b141ac26dfda55e48810aa410b4a1e000171418..21b4036277d55368b3c3952861e595362ba100e0 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Fri Dec  7 12:52:05 EST 2007
+Last updated:           Wed Dec 12 01:59:39 EST 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -947,14 +947,7 @@ first.  There is also a developer's wiki at
 Cache Usage
 
 
-  Allow free-behind capability for large sequential scans to avoid
-  kernel cache spoiling
-  Posix_fadvise() can control both sequential/random file caching and
-  free-behind behavior, but it is unclear how the setting affects other
-  backends that also have the file open, and the feature is not supported
-  on all operating systems.
-
-  Speed up COUNT(*)
+  Speed up COUNT(*)
   We could use a fixed row count and a +/- count to follow MVCC
   visibility rules, or a single cached value could be used and
   invalidated if anyone modifies the table.  Another idea is to