Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: chjischj(at)163(dot)com, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock
Date: 2018-11-08 01:49:31
Message-ID: CAH2-Wzkwr0hCQ0xSsFgjLXyKGhgF-JMsaqV9wOM0_xjZ6aU8tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 7, 2018 at 5:46 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I think that you have to be doing a multi-level delete for a deadlock
> to take place, which isn't particularly likely to coincide with a
> concurrent insertion in general. That may explain why it's taken a
> year to get a high-quality bug report.

BTW, it's notable that Chen's query uses ON CONFLICT DO UPDATE.
Speculative insertion might cause just the wrong kind of churn,
involving continual recycling of heap TIDs.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-11-08 01:50:35 Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT
Previous Message Peter Geoghegan 2018-11-08 01:46:52 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock