From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Oleksii Kliukin <alexk@hintbits.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date: Mon, 17 Jun 2019 10:32:11 +0900
Message-ID: <20190617013211.GB3153@paquier.xyz> (raw)
In-Reply-To: <4827.1560733813@sss.pgh.pa.us>
References: <20190617004002.GA2726@alvherre.pgsql>
<4827.1560733813@sss.pgh.pa.us>
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
Attachments:
[application/pgp-signature] signature.asc (832B, ../20190617013211.GB3153@paquier.xyz/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, alexk@hintbits.com, pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
In-Reply-To: <20190617013211.GB3153@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox