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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: 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 00:02:21
Message-ID: 32693.1560729741@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> I'm going to push the change of lifetime of the variable for now.

If you're going to push anything before tomorrow's wrap, please do it
*now* not later. We're running out of time to get a full sample of
buildfarm results.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-17 00:40:02 Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Previous Message Tom Lane 2019-06-16 19:39:21 pgsql: Release notes for 10.9, 9.6.14, 9.5.18, 9.4.23.

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-17 00:40:02 Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Previous Message Paul A Jungwirth 2019-06-16 22:59:29 Re: range_agg