> I believe the correct fix for this problem is for bufmgr.c to grab
> a read lock (BUFFER_LOCK_SHARED) on any page that it is writing out.
> A read lock is sufficient since there's no need to prevent other
> backends from reading the page, we just need to prevent them from
> changing it during the I/O.
> 
> Comments anyone?

Do it.

Vadim
 

Sun, 24 Sep 2000 17:39:26 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: Concurrent-update problem in bufmgr.c