aboutsummaryrefslogtreecommitdiff
path: root/src/backend/storage/buffer/README
diff options
context:
space:
mode:
Diffstat (limited to 'src/backend/storage/buffer/README')
-rw-r--r--src/backend/storage/buffer/README12
1 files changed, 5 insertions, 7 deletions
diff --git a/src/backend/storage/buffer/README b/src/backend/storage/buffer/README
index 498deb489d3..a2861b8db99 100644
--- a/src/backend/storage/buffer/README
+++ b/src/backend/storage/buffer/README
@@ -1,4 +1,4 @@
-$Header: /cvsroot/pgsql/src/backend/storage/buffer/README,v 1.2 2001/08/25 18:52:42 tgl Exp $
+$Header: /cvsroot/pgsql/src/backend/storage/buffer/README,v 1.3 2001/09/29 04:02:22 tgl Exp $
Notes about shared buffer access rules
--------------------------------------
@@ -30,12 +30,10 @@ Buffer locks: there are two kinds of buffer locks, shared and exclusive,
which act just as you'd expect: multiple backends can hold shared locks on
the same buffer, but an exclusive lock prevents anyone else from holding
either shared or exclusive lock. (These can alternatively be called READ
-and WRITE locks.) These locks are short-term: they should not be held for
-long. They are implemented as per-buffer spinlocks, so another backend
-trying to acquire a competing lock will spin as long as you hold yours!
-Buffer locks are acquired and released by LockBuffer(). It will *not* work
-for a single backend to try to acquire multiple locks on the same buffer.
-One must pin a buffer before trying to lock it.
+and WRITE locks.) These locks are intended to be short-term: they should not
+be held for long. Buffer locks are acquired and released by LockBuffer().
+It will *not* work for a single backend to try to acquire multiple locks on
+the same buffer. One must pin a buffer before trying to lock it.
Buffer access rules: