From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date: Thu, 13 Jun 2019 20:27:30 -0400
Message-ID: <20190614002730.GA12974@alvherre.pgsql> (raw)
In-Reply-To: <20190614.073229.1432207886733966773.t-ishii@sraoss.co.jp>
On 2019-Jun-14, Tatsuo Ishii wrote:
> I am a little bit confused. Here T1 and X are the same transaction?
Argh :-( Yes, X and T1 are the same transaction.
--
Á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-committers@postgresql.org
Cc: alvherre@2ndquadrant.com, ishii@sraoss.co.jp, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
In-Reply-To: <20190614002730.GA12974@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