RE: Concurrent-update problem in bufmgr.c

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: RE: Concurrent-update problem in bufmgr.c
Date: 2000-09-25 00:39:26
Message-ID: 8F4C99C66D04D4118F580090272A7A23018CF8@SECTORBASE1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-09-25 01:26:02 Re: psql's \d functions broken for views in current sources
Previous Message Tom Lane 2000-09-25 00:30:20 Re: Concurrent-update problem in bufmgr.c