| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:25:55 |
| Message-ID: | 20190617022555.GA20544@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2019-Jun-17, Michael Paquier wrote:
> 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?
Done.
I initially thought to keep the test in place, but then realized it
might be unstable, so I removed that too.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-17 02:27:25 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Alvaro Herrera | 2019-06-17 02:24:51 | pgsql: Revert "Avoid spurious deadlocks when upgrading a tuple lock" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-17 02:27:25 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Peter Geoghegan | 2019-06-17 02:14:05 | Re: nbtdesc.c and nbtpage.c are inconsistent with XLOG_BTREE_META_CLEANUP (11~) |