Skip to content

P
Postgres FD Implementation
Commit 2ed560c9 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Completed: 

> * -Cache last known per-tuple offsets to speed long tuple access
parent 9abced03
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 9 deletions
doc/TODO
View file @ 2ed560c9
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
TODO list for PostgreSQL TODO list for PostgreSQL
======================== ========================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Sun Mar 13 22:00:15 EST 2005 Last updated: Mon Mar 14 11:36:52 EST 2005
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.
...@@ -680,14 +680,7 @@ Cache ...@@ -680,14 +680,7 @@ Cache
* Consider use of open/fcntl(O_DIRECT) to minimize OS caching, * Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
especially for WAL writes especially for WAL writes
* Cache last known per-tuple offsets to speed long tuple access * -Cache last known per-tuple offsets to speed long tuple access
While column offsets are already cached, the cache can not be used if
the tuple has NULLs or TOAST columns because these values change the
typical column offsets. Caching of such offsets could be accomplished
by remembering the previous offsets and use them again if the row has
the same pattern.
* Speed up COUNT(*) * Speed up COUNT(*)
We could use a fixed row count and a +/- count to follow MVCC We could use a fixed row count and a +/- count to follow MVCC
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment