| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org, Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
| Subject: | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Date: | 2019-06-14 15:11:09 |
| Message-ID: | 20190614151109.GA12229@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2019-Jun-14, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Avoid spurious deadlocks when upgrading a tuple lock
>
> I'm now getting
>
> heapam.c: In function 'heap_lock_tuple':
> heapam.c:4041: warning: 'skip_tuple_lock' may be used uninitialized in this function
Hm, I don't get that warning. Does this patch silence it, please?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-14 15:25:32 | pgsql: Attempt to identify system timezone by reading /etc/localtime sy |
| Previous Message | Tom Lane | 2019-06-14 14:10:51 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2019-06-14 15:20:29 | Allow table AM's to cache stuff in relcache |
| Previous Message | Alvaro Herrera | 2019-06-14 14:38:55 | Re: pg_dump multi VALUES INSERT |