diff options
| author | Bruce Momjian <bruce@momjian.us> | 2005-03-14 16:37:02 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2005-03-14 16:37:02 +0000 |
| commit | 2ed560c99f031976e21937f6faa1c2d683d25b91 (patch) | |
| tree | dd51d0f015c40b4c5f4b0c658d63243dddf33050 | |
| parent | 9abced035d0925d59a791163aecc8f5214afff83 (diff) | |
| download | postgresql-2ed560c99f031976e21937f6faa1c2d683d25b91.tar.gz postgresql-2ed560c99f031976e21937f6faa1c2d683d25b91.zip | |
Completed:
> * -Cache last known per-tuple offsets to speed long tuple access
| -rw-r--r-- | doc/TODO | 11 |
1 files changed, 2 insertions, 9 deletions
@@ -2,7 +2,7 @@ TODO list for PostgreSQL ======================== 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 site, http://www.PostgreSQL.org. @@ -680,14 +680,7 @@ Cache * Consider use of open/fcntl(O_DIRECT) to minimize OS caching, especially for WAL writes -* 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. - +* -Cache last known per-tuple offsets to speed long tuple access * Speed up COUNT(*) We could use a fixed row count and a +/- count to follow MVCC |