| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "R, Siva" <sivasubr(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Duplicate Item Pointers in Gin index |
| Date: | 2018-02-21 03:31:12 |
| Message-ID: | CAH2-Wz=1jO+tFKrrN2y=9_0pNM7RLXC7ZfyzJsJ7b1gY+io6jA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 20, 2018 at 7:19 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-02-21 04:04:42 | Re: SHA-2 functions |
| Previous Message | Masahiko Sawada | 2018-02-21 03:19:45 | Re: Duplicate Item Pointers in Gin index |