Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit2ed560c

Browse files
committed
Completed:
> * -Cache last known per-tuple offsets to speed long tuple access
1 parent9abced0 commit2ed560c

File tree

1 file changed

+2
-9
lines changed

1 file changed

+2
-9
lines changed

‎doc/TODO

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
TODO list for PostgreSQL
33
========================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Sun Mar13 22:00:15 EST 2005
5+
Last updated:Mon Mar14 11:36:52 EST 2005
66

77
The most recent version of this document can be viewed at the PostgreSQL web
88
site, http://www.PostgreSQL.org.
@@ -680,14 +680,7 @@ Cache
680680

681681
* Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
682682
especially for WAL writes
683-
* Cache last known per-tuple offsets to speed long tuple access
684-
685-
While column offsets are already cached, the cache can not be used if
686-
the tuple has NULLs or TOAST columns because these values change the
687-
typical column offsets. Caching of such offsets could be accomplished
688-
by remembering the previous offsets and use them again if the row has
689-
the same pattern.
690-
683+
* -Cache last known per-tuple offsets to speed long tuple access
691684
* Speed up COUNT(*)
692685

693686
We could use a fixed row count and a +/- count to follow MVCC

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp