Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock(PG10.7)

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: chenhj <chjischj(at)163(dot)com>, 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(PG10.7)
Date: 2019-09-30 19:54:28
Message-ID: CAH2-WznOPWrgLbWucU=cZznAZmhAH8u4m7yhFLGQY_vB-YDEfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 29, 2019 at 8:12 AM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> I just managed to reproduce this using two sessions on master branch.
>
> session 1
> session 2

Was the involvement of the pending list stuff in Chen's example just a
coincidence? Can you recreate the problem while eliminating that
factor (i.e. while setting fastupdate to off)?

Chen's example involved an INSERT that deadlocked against VACUUM --
not a SELECT. Is this just a coincidence?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2019-09-30 19:55:54 Re: pgsql: Implement jsonpath .datetime() method
Previous Message Tom Lane 2019-09-30 19:36:11 Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro