From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Oleksii Kliukin <alexk@hintbits.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: upgrades in row-level locks can deadlock
Date: Thu, 13 Jun 2019 17:37:31 -0400
Message-ID: <20190613213731.GA11593@alvherre.pgsql> (raw)
In-Reply-To: <20190613180014.GA9775@alvherre.pgsql>
On 2019-Jun-13, Alvaro Herrera wrote:
> On 2019-Jun-13, Oleksii Kliukin wrote:
>
> > Makes sense. For the symmetry I have included those that perform lock
> > upgrades in one session and those that doesn’t, while the other sessions
> > acquire locks, do updates or deletes. For those that don’t upgrade locks the
> > test checks that the locks are acquired in the correct order.
>
> Thanks for the updated patch! I'm about to push to branches 9.6-master.
> It applies semi-cleanly (only pgindent-maturity whitespace conflicts).
Done, thanks for the report and patch!
I tried hard to find a scenario that this patch breaks, but couldn't
find anything.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, alexk@hintbits.com, pgsql-hackers@lists.postgresql.org
Subject: Re: upgrades in row-level locks can deadlock
In-Reply-To: <20190613213731.GA11593@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox