pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

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 11:44:20 +0900
Message-ID: <20190617024420.GA18917@paquier.xyz> (raw)
In-Reply-To: <7785.1560738445@sss.pgh.pa.us>
References: <20190617022555.GA20544@alvherre.pgsql>
	<7785.1560738445@sss.pgh.pa.us>

On Sun, Jun 16, 2019 at 10:27:25PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> On 2019-Jun-17, Michael Paquier wrote:
>>> Could you revert asap please then?
> 
>> Done.
> 
> Thanks.

Thanks, Alvaro.
--
Michael

Attachments:

  [application/pgp-signature] signature.asc (832B, ../20190617024420.GA18917@paquier.xyz/2-signature.asc)
  download

view thread (32+ messages)  latest in thread

Message-ID: <20190617024420.GA18917@paquier.xyz>
Permalink:  ../20190617024420.GA18917@paquier.xyz/
Also on:    postgresql.org/message-id/20190617024420.GA18917@paquier.xyz

copy link · copy postgr.es

reply

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: <20190617024420.GA18917@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