Return-Path: owner-postman
Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.37.53]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with ESMTP id VAA17680 for <postgres-arch>; Wed, 8 Mar 1995 21:48:40 -0800
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id VAA19193 for postgres-arch; Wed, 8 Mar 1995 21:48:36 -0800
Message-Id: <199503090548.VAA19193@faerie.CS.Berkeley.EDU>
X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol
From: aoki@CS.Berkeley.EDU (Paul M. Aoki)
To: postgres-arch@postgres.Berkeley.EDU
Reply-To: aoki@CS.Berkeley.EDU (Paul M. Aoki)
Subject: [andrew@postgres.Berkeley.EDU: sunita's bufmgr bug]
Date: Wed, 08 Mar 95 21:48:36 -0800
Sender: aoki@postgres.Berkeley.EDU
X-Mts: smtp

------- Forwarded Message

 From:  "Andrew K. Yu" <andrew@postgres.Berkeley.EDU>
 To:  aoki@postgres.Berkeley.EDU
 Cc:  andrew@postgres.Berkeley.EDU
 Subject:  sunita's bufmgr bug
 Date:  Wed, 8 Mar 1995 15:33:28 -0800

 
 hey Paul, we seem to have found the bug (that you introduce last July while
 you're optimizing the bufmgr). The bug occurs when BufferReplace releases 
 the lock and before it gets to insert the new tag into the buffer table
 (because it's flushing out a dirty buffer), someone else could have allocated
 another buffer for the same block. And when BufferReplace try to insert the
 new tag, it's already there...
 
 -andrew

------- End of Forwarded Message
--
  Paul M. Aoki          |  University of California at Berkeley
  aoki@CS.Berkeley.EDU  |  Dept. of EECS, Computer Science Division (#1776) 
                        |  Berkeley, CA 94720-1776