Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date: 2019-06-14 00:27:30
Message-ID: 20190614002730.GA12974@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2019-06-14 00:41:14 pgsql: Fix typos and inconsistencies in code comments
Previous Message Michael Paquier 2019-06-14 00:10:41 pgsql: Use OpenSSL-specific ifdefs in sha2.h