Postgres Pro
Downloads
Home   >   mailing lists

Re: Duplicate Item Pointers in Gin index - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Duplicate Item Pointers in Gin index
Date
Msg-id CAH2-Wz=1jO+tFKrrN2y=9_0pNM7RLXC7ZfyzJsJ7b1gY+io6jA@mail.gmail.com
Whole thread Raw
In response to Re: Duplicate Item Pointers in Gin index  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Duplicate Item Pointers in Gin index  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Feb 20, 2018 at 7:19 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> IIUC, ginInsertCleanup() holds ExclusiveLock on metapage during adding
> tuples in the pending list to the accumulator. And inserting entries
> to the pending list also requires ExclusiveLock on metapage. This
> behavior is not relevant with that bug fix. So I don't think that
> backend2 can inserts a tuple while backend1 is processing the pending
> list.

You mean that you think that the problem that Siva described cannot
happen once Postgres has commit
3b2787e1f8f1eeeb6bd9565288ab210262705b56?

-- 
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Duplicate Item Pointers in Gin index
Next
From: Michael Paquier
Date:
Subject: Re: SHA-2 functions