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

From Tom Lane
Subject Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date
Msg-id 32693.1560729741@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: Re: range_agg
Next
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock