summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2004-11-08 20:16:20 +0000
committerBruce Momjian2004-11-08 20:16:20 +0000
commit916897cce73fcce0579bbc591af6333904f64c9e (patch)
tree6d19ebc990dbbb66053cde44004607385214b3f4
parentcd6ecf6829e813c91dd38eeafefb647775cb2314 (diff)
Update:
< posix_fadvise() [fadvise] > posix_fadvise() > > 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. >
-rw-r--r--doc/TODO10
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/TODO b/doc/TODO
index 4c6e04ab3ac..d32a5ca7a11 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -6,7 +6,7 @@ TODO list for PostgreSQL
Bracketed items "[]" have more detail.
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Mon Nov 8 10:32:30 EST 2004
+Last updated: Mon Nov 8 15:16:11 EST 2004
The most recent version of this document can be viewed at the PostgreSQL web
site, http://www.PostgreSQL.org.
@@ -644,7 +644,13 @@ Fsync
Cache
=====
* Allow free-behind capability for large sequential scans, perhaps using
- posix_fadvise() [fadvise]
+ posix_fadvise()
+
+ 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.
+
* Consider use of open/fcntl(O_DIRECT) to minimize OS caching
* Cache last known per-tuple offsets to speed long tuple access