BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty().

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Subject: BUFFER_LOCK_EXCLUSIVE is used in ginbuildempty().
Date: 2014-07-16 08:13:04
Message-ID: 20140716.171304.232876096.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

As far as I see gin seems using GIN_EXCLUSIVE instead of
BUFFER_LOCK_EXCLUSIVE for LockBuffer, but the raw
BUFFER_LOCK_EXCLUSIVE appears in ginbuildempty().

Does it has a meaning to fix them to GIN_EXCLUSIVE?

regards,

--
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
gin_buffer_lock_exclusive.patch text/x-patch 723 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2014-07-16 08:41:37 Re: [bug fix] pg_ctl always uses the same event source
Previous Message Kyotaro HORIGUCHI 2014-07-16 08:04:59 [BUG?] tuples from file_fdw has strange xids.