From 219c024c64ced7ce497fe455b1e3dd7b70012775 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Tue, 22 May 2012 09:30:59 -0400 Subject: [PATCH] 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. --- src/backend/storage/buffer/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/storage/buffer/README b/src/backend/storage/buffer/README index 38e67c1c90..6fd961206b 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