| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | 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 01:10:13 |
| Message-ID: | 4827.1560733813@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-Jun-16, Tom Lane wrote:
>> 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.
> Yeah, I had to bail out earlier today, so the only thing I'm confident
> pushing now is a revert.
Yeah, let's do that. I don't want to risk shipping broken code.
We can try again for the next updates.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-17 01:32:11 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Alvaro Herrera | 2019-06-17 00:40:02 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-17 01:30:59 | nbtdesc.c and nbtpage.c are inconsistent with XLOG_BTREE_META_CLEANUP (11~) |
| Previous Message | Alvaro Herrera | 2019-06-17 00:40:02 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |