database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

TODO item not needed anymore now that the buffer cache is

Browse Source 
scan-resistant:

<
< * Allow free-behind capability for large sequential scans, perhaps using
<   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
2007-06-02 02:46:38 +00:00
parent 15f8202c20
commit ededa6dfc8
2 changed files with 3 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/TODO
View File

@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Fri Jun 1 14:41:49 EDT 2007
Last updated: Fri Jun 1 22:46:01 EDT 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -1090,14 +1090,6 @@ Fsync
Cache Usage
===========
* Allow free-behind capability for large sequential scans, perhaps using
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.
* Speed up COUNT(*)
We could use a fixed row count and a +/- count to follow MVCC