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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Oleksii Kliukin <alexk(at)hintbits(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date: 2019-06-17 01:32:11
Message-ID: 20190617013211.GB3153@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sun, Jun 16, 2019 at 09:10:13PM -0400, Tom Lane wrote:
> Yeah, let's do that. I don't want to risk shipping broken code.
> We can try again for the next updates.

Could you revert asap please then?
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-17 02:24:51 pgsql: Revert "Avoid spurious deadlocks when upgrading a tuple lock"
Previous Message Tom Lane 2019-06-17 01:10:13 Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-06-17 01:54:57 Re: nbtdesc.c and nbtpage.c are inconsistent with XLOG_BTREE_META_CLEANUP (11~)
Previous Message Michael Paquier 2019-06-17 01:30:59 nbtdesc.c and nbtpage.c are inconsistent with XLOG_BTREE_META_CLEANUP (11~)