Re: BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty(). - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty().
Date
Msg-id CAM3SWZTvA1bWVA+4m=edmY7q2R383gpwaKTp0QW+5mC3xAQSng@mail.gmail.com
Whole thread Raw
In response to Re: BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty().  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty().  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jul 17, 2014 at 7:47 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> I don't understand the point of having these GIN_EXCLUSIVE / GIN_SHARED
> symbols.  It's not like we could do anything different than
> BUFFER_LOCK_EXCLUSIVE etc instead.  It there was a GinLockBuffer() it
> might make more sense to have specialized symbols, but as it is it seems
> pointless.

It's a pattern common to the index AMs. I think it's kind of pointless
myself, but as long as we're doing it we might as well be consistent.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty().
Next
From: Tom Lane
Date:
Subject: Portability issues in TAP tests