aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2012-05-22 09:30:59 -0400
committerRobert Haas <rhaas@postgresql.org>2012-05-22 09:32:09 -0400
commit219c024c64ced7ce497fe455b1e3dd7b70012775 (patch)
tree55d292730ae948851915d499a36092a96032272d /src
parentb94ce6e807ce5685bda1dcd36027091ceec6b5a0 (diff)
downloadpostgresql-219c024c64ced7ce497fe455b1e3dd7b70012775.tar.gz
postgresql-219c024c64ced7ce497fe455b1e3dd7b70012775.zip
Repair out-of-date information in src/backend/storage/buffer/README.
In commit d526575f893c1a4e05ebd307e80203536b213a6d, we changed things so that buffer usage counts are incremented when the buffer is pinned, rather than when it is unpinned, but the README file didn't get the memo. Report by Amit Kapila.
Diffstat (limited to 'src')
-rw-r--r--src/backend/storage/buffer/README4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/storage/buffer/README b/src/backend/storage/buffer/README
index 38e67c1c905..6fd961206b5 100644
--- a/src/backend/storage/buffer/README
+++ b/src/backend/storage/buffer/README
@@ -169,8 +169,8 @@ need to take system-wide locks during common operations. It works like
this:
Each buffer header contains a usage counter, which is incremented (up to a
-small limit value) whenever the buffer is unpinned. (This requires only the
-buffer header spinlock, which would have to be taken anyway to decrement the
+small limit value) whenever the buffer is pinned. (This requires only the
+buffer header spinlock, which would have to be taken anyway to increment the
buffer reference count, so it's nearly free.)
The "clock hand" is a buffer index, NextVictimBuffer, that moves circularly