mirror of
https://github.com/postgres/postgres.git
synced 2025-07-31 22:04:40 +03:00
Re-add TODO and clarify it is for the kernel cache:
< * Allow free-behind capability for large sequential scans, perhaps using < posix_fadvise() > * Allow free-behind capability for large sequential scans to avoid > kernel cache spoiling
This commit is contained in:
10
doc/TODO
10
doc/TODO
@ -1,7 +1,7 @@
|
||||
PostgreSQL TODO List
|
||||
====================
|
||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||
Last updated: Fri Jun 1 22:46:01 EDT 2007
|
||||
Last updated: Sat Jun 2 07:27:46 EDT 2007
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
||||
@ -1090,6 +1090,14 @@ 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
|
||||
|
Reference in New Issue
Block a user