<   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.
>
This commit is contained in:
Bruce Momjian 2004-11-08 20:16:20 +00:00
parent cd6ecf6829
commit 916897cce7
1 changed files with 8 additions and 2 deletions

View File

@ -6,7 +6,7 @@ TODO list for PostgreSQL
Bracketed items "[]" have more detail. Bracketed items "[]" have more detail.
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) 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 The most recent version of this document can be viewed at the PostgreSQL web
site, http://www.PostgreSQL.org. site, http://www.PostgreSQL.org.
@ -644,7 +644,13 @@ Fsync
Cache Cache
===== =====
* Allow free-behind capability for large sequential scans, perhaps using * 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 * Consider use of open/fcntl(O_DIRECT) to minimize OS caching
* Cache last known per-tuple offsets to speed long tuple access * Cache last known per-tuple offsets to speed long tuple access