| 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 02:44:20 |
| Message-ID: | 20190617024420.GA18917@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sun, Jun 16, 2019 at 10:27:25PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> On 2019-Jun-17, Michael Paquier wrote:
>>> Could you revert asap please then?
>
>> Done.
>
> Thanks.
Thanks, Alvaro.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-17 07:15:24 | pgsql: Fix more typos and inconsistencies in the tree |
| Previous Message | Tom Lane | 2019-06-17 02:27:25 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2019-06-17 03:04:51 | RE: Speed up transaction completion faster after many relations are accessed in a transaction |
| Previous Message | Tom Lane | 2019-06-17 02:27:25 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |