| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 00:40:02 |
| Message-ID: | 20190617004002.GA2726@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2019-Jun-16, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > I'm going to push the change of lifetime of the variable for now.
>
> 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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-17 01:10:13 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Tom Lane | 2019-06-17 00:02:21 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-17 01:10:13 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Tom Lane | 2019-06-17 00:02:21 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |