Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbmv0-0004BN-0z for pgsql-committers@arkaria.postgresql.org; Fri, 14 Jun 2019 14:11:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hbmuy-0004kA-S5 for pgsql-committers@arkaria.postgresql.org; Fri, 14 Jun 2019 14:11:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbmuy-0004ic-I6 for pgsql-committers@lists.postgresql.org; Fri, 14 Jun 2019 14:11:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbmuv-0003fr-Hp for pgsql-committers@lists.postgresql.org; Fri, 14 Jun 2019 14:10:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x5EEAppk002817; Fri, 14 Jun 2019 10:10:52 -0400 From: Tom Lane To: Alvaro Herrera cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock In-reply-to: References: Comments: In-reply-to Alvaro Herrera message dated "Thu, 13 Jun 2019 21:32:14 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2814.1560521451.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 14 Jun 2019 10:10:51 -0400 Message-ID: <2815.1560521451@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera 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 thi= s function Please fix. regards, tom lane