Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date
Msg-id 20190614002730.GA12974@alvherre.pgsql
Whole thread Raw
In response to Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List 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



pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Use OpenSSL-specific ifdefs in sha2.h
Next
From: Michael Paquier
Date:
Subject: pgsql: Fix typos and inconsistencies in code comments