Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Date: 2019-06-14 14:10:51
Message-ID: 2815.1560521451@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

Please fix.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-14 15:11:09 Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Previous Message Bruce Momjian 2019-06-14 13:30:35 pgsql: doc: PG 12 relnotes, add mention of single-child optimization

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-06-14 14:13:28 Re: pg_dump multi VALUES INSERT
Previous Message Bruce Momjian 2019-06-14 13:30:41 Re: PostgreSQL 12: Feature Highlights