Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
2ed560c9
Commit
2ed560c9
authored
20 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Completed:
> * -Cache last known per-tuple offsets to speed long tuple access
parent
9abced03
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/TODO
+2
-9
2 additions, 9 deletions
doc/TODO
with
2 additions
and
9 deletions
doc/TODO
+
2
−
9
View file @
2ed560c9
...
...
@@ -2,7 +2,7 @@
TODO list for PostgreSQL
========================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated:
Su
n Mar 1
3 22:00:15
EST 2005
Last updated:
Mo
n Mar 1
4 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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment